*** This bug is a duplicate of bug 172400 ***
https://bugs.launchpad.net/bugs/172400
** This bug has been marked a duplicate of bug 172400
pam modules need dynamic 32-bit support and are missing from ia32-libs
* You can subscribe to bug 172400 by following this link:
I think this is the same bug as
https://bugs.edge.launchpad.net/ubuntu/+source/ia32-libs/+bug/172400
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is still an issue. I'm running ubuntu 9.04 and vmware server 1.0.9 and I
can't get pam authorization to work. The only way I could use the remote
console is to disable pam auth altogether. If anyone has any ideas I'd be glad
to try them out.
Thanks!
--
vmware server will not connect
I went back to 8.04 or so and it works then. Sadly, 9.04 and possibly
even 8.10 don't work :(
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Let me guess, a Nehalem box and you need the igb drivers? :)
If so, go nominate this and comment
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/352440
I'm trying to get proper drivers backported to LTS, other people are
too, apparently it's there but not a good enough
Thanks for the reply. Unfortunately the hardware I'm using requires me
to run 9.04...
-- Original Message --
From: mshadle launch...@mike2k.com
Date: Wednesday, August 5th, 2009 2:35 PM PDT
To: t...@mccnet.com
Subject: [Bug 112937] Re: vmware server will not connect remotely
I went back
Glad to hear I'm not the only one. I too have been attempting 1.0.9
with no success. What I find odd is that I can connect as an
unprivileged user but not as root.
If only we could get the -current- version of Ubuntu to behave, now.
Yes!!
--
vmware server will not connect remotely
I will say this
I tried 9.04, could not get it to work. Same with 8.10.
However, I did 8.04.2, and it worked, out of the box, without even
requiring the vmware patch / vmware-update-update thingy. I can connect
remotely to it too, without tweaking pam at all even.
This is vmware server 1.0.9
Does not work using VMware server 1.0.9 downloaded from vmware directly.
It compiles, using the vmware-any-any-update or vmware-update for the
kernel and such. However, remote connectivity still triggers the PAM
errors.
I have tried on both 9.04 and 8.10 Ubuntu 64-bit, roughly the same
message
** Changed in: ia32-libs (Ubuntu)
Importance: Undecided = Wishlist
Status: New = Triaged
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The solution at
https://bugs.launchpad.net/ubuntu/+bug/112937/comments/11 worked for me
on 8.04.1 amd64.
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
whoops! spoke too soon. I'm actually using vmware server 2 beta. The
above worked well enough to get to the login screen but not to
authenticate, probably because it included common but not enough other
modules. Here is the pam config which works for me.
auth sufficient pam_unix.so shadow nullok
This is really a pam bug.
vmware-server uses pam as shipped in ia32-libs. pam hardcodes the
/lib/security path, but on amd64 installations, this is where the 64-bit
pam modules are, so we end up with a 32 bit application tryin to dlopen
a 64 bit binary, which obviously doesn't work. What needs to
We'll also need to add libpam-modules to ia32-libs.
** Also affects: ia32-libs (Ubuntu)
Importance: Undecided
Status: New
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which
Confirmed with Gutsy x64. The above fix worked.
Thanks guys.
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ronnie Redd wrote:
OK,
(Please note the corrected path here - /etc/pam.d/vmware-authd instead of
/etc/pam.dvmware-authd)
I went for it and I too confirm that the below fixes it on AMD64 Gutsy:
replace the pam configuration in /etc/pam.d/vmware-authd to read:
auth sufficient
Just confirming AMD64 Gutsy that the following fixes the issue?
replace the pam configuration in /etc/pam.dvmware-authd with:
auth sufficient /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix.so
shadow nullok
auth required /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix_auth.so
OK,
(Please note the corrected path here - /etc/pam.d/vmware-authd instead of
/etc/pam.dvmware-authd)
I went for it and I too confirm that the below fixes it on AMD64 Gutsy:
replace the pam configuration in /etc/pam.d/vmware-authd to read:
auth sufficient
I can confirm the problem with gutsy AMD64. The solution from Walter
works for me.
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
On gutsy AMD64 deb package the solution above of including common-auth and
common-account DOES NOT work for
me. Instead I had to replace the pam configuration with:
auth sufficient
/usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix.so shadow nullok
auth required
** Changed in: ubuntu
Assignee: (unassigned) = VMware Build Team (vmware-builds)
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Dominique ,
both solutions work just as well for me.
However I have to say yours is much more elegant.
Thank you for the insight.
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm that Dominique's solution worked for me. I can now
remotely configure and use vmware from another machine, logging in using
the same username and password as my ubuntu login. Thanks Dominique!
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You
I can confirm that there is a pam problem with vmware server.
** Changed in: Ubuntu
Importance: Undecided = Low
Status: New = Confirmed
--
vmware server will not connect remotely
https://bugs.launchpad.net/bugs/112937
You received this bug notification because you are a member of
The solution of Purity Control was not working on my fresh installation of
ubuntu 7.04 ( server ).
I solved it by setting the content of the file /etc/pam.dvmware-authd with
#%PAM-1.0
@include common-auth
@include common-account
This solved everything. ( in fact it is the content of the file
I am running Feisty32 on the vmware server machine (vmware-server
(1.0.3-1 ) in feisty-commercial module), and Feisty64 on the vmware
client.
I get this error when trying to connecto to
Unable to connect to the remote host: Login (username/password)
incorrect
The same username/password works
Hi Wilbur,
I am no linux expert, I am just the person who originally tried to file
the bug but if you follow my instructions in the first post with the
modification describe below, I think you may have success. I have only
tried it on 32 bit installs but it has worked on all of those and I
cannot
With vmware-server (1.0.3-1 ) in feisty-commercial module
/etc/pam.d/vmware-authd contains:
#%PAM-1.0
auth sufficient
/usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix2.so shadow nullok
auth required
28 matches
Mail list logo
