Do you have a firewall turned on? Try as a temp solution to turn that off.
Another thing you should check is if you are allowed to login as root? Check your SELinux Settings in yast.
Can you ssh into the system?
I may be way off... But those are some starting points.
I have the same problem with a suse 10.2 system. I can't login with either my root or user id's.
Nov 13 10:52:40 giladrial vmware-authd: pam_unix(vmware-authd:auth): authentication failure; logname= uid=30 euid=0 tty= ruser= rhost= user=wcn00
Nov 13 10:56:17 giladrial vmware-authd: pam_unix(vmware-authd:auth): authentication failure; logname= uid=30 euid=0 tty= ruser= rhost= user=root
I can ssh and to that machine with either id.
BTW I could not access the web interface untill after I disabled ipv6, rebooted and reran the vmwar-config.pl script.
I think the PAM module is broken.
So after you removed ipv6 were you able to get access?
I dont have ipv6 active on my box and i still can't get into the console.
ps: i can login with ssh with all the id's i have tried and i have no firewall active.
No the IPV6 thing is just an ancilliary issue.
Its in the release notes.
I still don't have remote access with either the web access or the vmware console.
Further to this, if In install the 1.04 console on the machine with the beta version of server (which is running) and try to connect to the local vmware I get a popup with:
The local VMware Server is not installed, or is not currently running.
Make sure that the server is properly installed and try again.
I suppose its worth mentioning that I'm doing all this over an NX client session because the vmware server host machine does not have a monitor.
Sorry took so long.
Is the vmware-authd service starting? Check your kernel logs (alt+f10) see if anything is tainting the kernel.
I am having a similar issue using opensuse 10.2 it only works after I recompile.... Rebooting takes away the changes and I have to recompile. And on my system the kernel log shows that authd is tainting the kernel.
I will be testing this on an updated kernel and see if that takes care of this.... Will let you know.
I have no list of tainted modules being loaded on the kernel.
Any more ideas?
Do you have the pam modules 32 bit installed
There is/was a problem on the old server v1 on Suse 64 Bit
Hope this helps,
Yes i have, and vmware 1.0X works without any problem. The problem appears to be in the 2.0 version
I had 1.0.4 installed with no problem. When I upgraded the rpm that is when the fun started.
The first issue was no console access to vm's. Then I uninstalled the rpm and reinstalled the rpm re-ran the vmware-config.pl script then I was encountering the vmm failing which gave me what sounded like the same issue of not being able to log in. I then ran the 1.0.4 rpm and the vmware-config.pl script again replacing the 2.0 rpm. Then re-ran the upgrade and vmware-config.pl script. I am able to use the product but there are a few bugs that need to be fixed.
This is painful at the least I guess if a reinstall does not fix the problem you can create an account and submit a trouble ticket, or revert to 1.0.4.
I had the same issue but after uninstalling, installing 1.0.4 running the vmware-config.pl script, and upgrading to 2.0 again and running the vmware-config.pl script is when my issue cleared up.
Trying a reinstall is the only thing besides opening a trouble ticket with VMware.
I've just upgraded the kernel for debug sake and the problem remains
Nov 15 09:27:15 npar1 /usr/lib/vmware/bin/vmware-hostd: Rejected password for user root from 127.0.0.1
Nov 15 09:27:33 npar1 /usr/lib/vmware/bin/vmware-hostd: pam_unix(vmware-authd:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root