Error opening the remote virtual machine-the host name could not be resolved

In the previous post we created a virtual machine which is going to host our Windows Server 2003 for the domain controller of our testing network. you can read the how-to post here “creating a virtual machine on VMware”

If you had installed VMware server the way I did, you most likely encountered an error when going to the console tab and try to install the OS on the virtual machine. the error reads “Error opening the remote virtual machine 8333\16 the host name could not be resolved”

The problem lies in the URL you use to login to the VMware server console. the default URL that VMware server creates is like https://nelson-pc:8333/ui/# if you substitute the computer name for “localhost” that should fix the problem. The URL to login to the VMware server console should be https://localhost:8333/ui/#.

Change your VMware default login shortcut URL to reflect this new path. Now you should be ready to initiate the OS installation on your virtual machine, that will be the topic of our next post. stay tuned.

20 Comments Already

Guillermo Said,

July 1st, 2008 @11:34 am

Thanks for the help

Sebastian Said,

August 9th, 2008 @1:14 pm

Hi,
configuring a new VM works fine. Even my old VM seem to work.

So I hit the start-button for my new VM, th system tells me everything works, but i cant connect to the remote console.

I’ve tryed direktly by clicking on the console tab->somewhere in the window.
That way i get the error described above.

If i enter https://”my IP”:8333/ui/”#” tomcat tells me site does not exist.

So what els can i do to connect to my VM ?

Eriq Said,

August 26th, 2008 @5:01 pm

This did-not resolve my issue. It seems to have helped with som other issues I was having, but I still get the error opening the remote virtual machine…

~Q~

Derek Gabriel Said,

August 30th, 2008 @4:30 am

Same error, it just switched the base URL:

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

It appears that whatever mechanism populates the code for the console isn’t parsing the URL properly. Considering I just installed VMware server for the first time, I’ll dig around and see if I can come up with something, but I’m a little over my head in that area.

August 30th, 2008 @4:55 am

The answer is actually of all places in the known issues documentation. You need to add a line to your hosts files:
127.0.0.1 localhost

and the second I saved the hosts file, fixed.

August 30th, 2008 @4:56 am

crap, the other parts of that didn’t show
127.0.0.1 localhost hostname hostname.fqdn

I’ve removed the brackets that made it dissapear on my last post.

Alan Said,

August 31st, 2008 @1:28 pm

Derek’s solution worked for me.

Docomo Said,

September 2nd, 2008 @7:02 am

Good one! Works for me as well.

Ben Said,

September 3rd, 2008 @11:59 am

don’t work for me

Richard Said,

September 10th, 2008 @5:57 am

Does not work for me plus 127.0.0.1 localhost is already in my host file, anyone actually solved this

Felix Said,

September 10th, 2008 @6:06 pm

make sure only “127.0.0.1 localhost” in hosts file, I removed everything else vm server added in there, and it works fine.

Rod Dines Said,

September 13th, 2008 @5:05 am

I got mine to work by adding to host file this line
127.0.0.1 [short server name]

Note that was the name I used when installing the VMWARE SERVER

Dave Said,

September 14th, 2008 @10:46 am

Thanks, Felix’s tip solved if for me.
Hosts file in windows is at: C:\Windows\System32\drivers\etc
I just commented out the bogus line that was added after the 12.7.0.0.1 rule: #::1 localhost

Bomb^49 Said,

September 29th, 2008 @10:38 am

I had the same problem in Windows Vista. The way I solved it was:

Click Start =>
Right click on Computer =>
Click Manage =>
On the Left side there is a tree view, expand Services and Applications =>
Below, click Services =>
In the right panel, scroll down until you find “VMWare Host Agent” in the list =>
Right click on it, then click Start =>
Wait until it finishes starting it =>
Find “VMWare VSS Writer” in the list =>
Right click on it, then click Start =>
Wait until it finishes starting it =>
Open https://localhost:8333/ui/# in your internet browser (I’m using FireFox) =>
In FireFox you should see something like: “Secure Connection Failed”, click “Or you can add an exception”¦” =>
Click “Add Exception…” =>
Click “Get Certificate” =>
Click “Confirm Security Exception” =>
You should now see a login box in the middle of the page, make sure your an admin on your computer, then login with your computer’s username and password =>
You should now be in the VMWare Server Control Panel!

September 29th, 2008 @12:50 pm

Also, if you want to make it where you don’t have to start the “VMWare Host Agent” and “VMWare VSS Writer” service every time Windows starts up:

Right click on “VMWare VSS Writer” under “Services” =>
Click on “Properties” =>
In the “Startup Type” dropdown box, select “Automatic” =>
Click “Apply” =>
Click “OK” =>
Done!