VMWare Server 2 Beta fails to connect to virtual machine with "Error opening the remote virtual machine [machine] The host name could not be resolved."

20. May 2008
Comments (2)

I've just upgraded my VMWare Server install to the latest version of the VMWare Server beta, which I have to say, is looking pretty good! One slight niggle that I had was that when I opened the VMWare Remote Console it would tell me that I could not connect, with the error:

Error opening the remote virtual machine SM-00109:8333\16:  The host name could not be resolved.

Clearly THAT's a pain in the proverbial. A quick trawl through VMWare's forums reveals two solutions, one that is clunky and stupid, the other that works. For brevity, the one that works is...

Use the fully qualified domain name of the computer to connect to the VMWare console, so for me, that mean using:

https://SM-00109.domain.dom:8333

instead of

https://SM-00109:8333

Simple!

VMWare

Comments

Karam Abuataya
Karam Abuataya
9/11/2008 11:27:54 AM #
i am not joines to any domain so i really don't have a fully qualified name, what to do?
SamMcGeown
SamMcGeown
10/24/2008 11:51:40 AM #
When you installed VMWare Server you went through a step which asked for a FQDN - whatever you put in there should work. Other things you could try, if you're in a workgroup, try computername.workgroupname. You can also open a command prompt, run ipconfig /all and look at the host name and the primary DNS suffix and put the two together to get your FQDN.

Sam
Comments are closed