Hi guys
Environment: MS XP Pro SP2, VMWare Server 1.0.1 build-29996
Having just installed VMWare Server I get this error each time I try to connect to Localhost:
511 Error connecting to C:\Program Files\VMware\VMware Server\vmserverdWin32.exe process.
All services are started (and have been restarted):
VMware Authorization Service
VMware DHCP Service
VMware NAT Service
VMware Registration Service
Each time I try to connect to Localhost my Application Event Viewer get flooded with messages like this:
The description for Event ID ( 100 ) in Source ( vmauthd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Failed to read registry perf object Memory\Cache Bytes.
The perf objects that can't be read are:
Memory\Cache Bytes
Process\ID Process
Memory\Page Faults/sec
Memory\Pool Nonpaged Bytes
Memory\Pool Paged Bytes
Memory\Committed Bytes
I also get this message in my Event Viewer:
Failed to impersonate vmware user (error 6).
Can anyone shed some light over this as I would hate to have to use a competing piece of software...
/cjessing
I was having the same problem on my XP SP2 machine. Make sure that your Netlogon service is started.
Hi,
i have the same problem with Re: Help: 511 Error connecting to C:\Program...\vmserverdWin32.exe process."511 Error connecting to C:\Program Files (x86)\VMware\VMware Server\vmserverdWin32.exe process."[/i] and Re: Help: 511 Error connecting to C:\Program...\vmserverdWin32.exe process."The description for Event ID ( 100 ) in Source ( vmauthd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Failed to impersonate vmware user (error 6)."[/i]
If i try to start the Netlogon service i get:
Re: Help: 511 Error connecting to C:\Program...\vmserverdWin32.exe process."The Net Logon service on a Local Computer started and then stooped. Some services stop automatically if they have no work to do, for example the Performance Logs and Alerts service."[/i]
I checked the local policies ("Allow log on locally").
Can anyone help me?
(Running XP Professional x64 Edition Version 2003 SP 1
VMware Server Console Verison 1.0.2 build-39867)
>>Make sure that your Netlogon service is started.
The netlogon service is only needed on a domain member. If it's a standalone workstation / server, you'll not be able to start it.
Please, search the forum. The problem is a known one; there are some workarounds there...
Hi,
i already searched the forums:
__vmware_user__ has to be in the group "administrators" -> still "impersonate"-error
install IIS, stop default site, use web interface -> still "impersonate"-error
change local policies to allow log on locally -> still "impersonate"-error
Install after install with repair option -> still "impersonate"-error
reboot machine -> still "impersonate"-error
So any other hints?
We'll start over...
You installed the VMware server as local admin, right? Not a domain user with admin rights, but as a real Re: Help: 511 Error connecting to C:\Program...\vmserverdWin32.exe process.local[/i] admin?
If not, deinstall the product and install it as a local admin.
Now, find the two services:
VMware Authorisation Service
VMware Registration Service
and set them to start manually.
Reboot.
Run the following at the command prompt:
Re: Help: 511 Error connecting to C:\Program...\vmserverdWin32.exe process.net start "VMware Registration Service"[/code]
Please type the command as is, including ticks.
See, if you get any errors. If not, the server is usable now. We'll only need to automate the starting.
If not, then please reinstall Windows and start over.
>>__vmware_user__ has to be in the group "administrators"
No, please don't do it.
>>change local policies to allow log on locally
For which user? Please don't touch the __vmware_user__
Hi,
just to clarifiy:
i am working on a xp machine which is member of a linux/kerberos domain.
A real local admin is the user "administrator" from this local machine?
Not a local user which is member of the group administrators?
In other words: i have to login with "administrator" and domain = "myhostname" and not "mykerberos.realm"?
Tomorrow morning i will do this.
Hi,
just to clarifiy:
i am working on a xp machine which is member of a
linux/kerberos domain.
A real local admin is the user "administrator" from
this local machine?
Not a local user which is member of the group
administrators?
In other words: i have to login with "administrator"
and domain = "myhostname" and not
"mykerberos.realm"?
Yes! Log in as "administrator" from this local machine.
Hi,
the services started successfully, but still the 511-error.
Now i am starting a new installation of windows ;-(
No more 511...
Windows XP 64 Bit without kerberos....
I think there is a small bug for the authentication of the __vmware_user__. The user does not authenticate as local user if another realm is there...
Perhaps this could be fixed ![]()
>>I think there is a small bug for the authentication of the __vmware_user__. The user does not authenticate as local user if another realm is there...
I can't confirm that on a 32 bit W2K3. Running VMware Server successfully on a domain (real W2K3) member.
I know this thread is old, but I didn't see a resolution that solved my similar problem, short of "reinstall Windows." My problem ended up being that I didn't have the Client for Microsoft Networks installed for my hardware network interface. Once I installed that, I could start up the VMware Server Console.
Shameless (or shameful?) Plug I've outlined it on my blog.
http://bunglingsysadmin.blogspot.com/2008/09/vmware-startup-problems-511-error.html
I was afraid that running it on my DC was causing this issue - (no local logon). But it was resolved as soon as I disabled the Default Website.
The solution is in restarting the Vmware authorization service and Vmware registration service. That helps me...