Poll

Which programming language do you prefer?
 
Feed Your Need!

About Me

My name is Romeo Dumitrescu

I am a Software Developer for Macadamian Technologies

Downloads

No Documents

Who's Online

We have 1 guest online
VMware Server - The VMware Infrastructure Web Service is not responding - Connection Refused PDF Print E-mail
User Rating: / 8
PoorBest 
Other - Work Related
Written by Romeo Dumitrescu
  
Wednesday, 25 March 2009 07:38

When running VMware server on an OS with IPv6 enabled, you might get the following error after logging in to the server web UI:

The VMware Infrastructure Web Service at "http://localhost:8222/sdk" is not responding (Connection Refused).

The service may not be responding because hostd is too busy or because it is not running. Try again in a few moments or restart hostd.
Until communication with the VI Web Service is restored, VI Web Access will not be able to manage any hosts.
More Informationbq. Details
ConnectException : Operation failed.

 

While the error details are not very explicit, the reason for the error is very simple: the IPv6 lookup for “localhost” is not supported by the server.
To fix this you have to edit the hosts file and add an IPv4 host entry for “localhost”.

The hosts file is in C:\Windows\System32\Drivers\etc
Open the file with Notepad and add the following line:

 
127.0.0.1       localhost

Your hosts file should look somewhat like this.

# Copyright (c) 1993-2006 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
 
 
::1             localhost
127.0.0.1       localhost
 

After this, just reboot to make sure that all the services are aware of the change. You shouldn’t get that error anymore (unless there is another problem with the service).

Comments
Add New Search
Grace 2009-07-03 13:29:02

Excellent!
Thanks so much. You saved me.
Excellent!
Michael Brassway 2009-03-25 21:57:50

I was looking for a solution to this for ages. No wonder it failed...
Thank you
very much!
Write comment
Name:
Email:
 
Title:
UBBCode:
[b] [i] [u] [url] [quote] [code] [img] 
 
:angry::0:confused::cheer:B):evil::silly::dry::lol::kiss::D:pinch::(:shock::X:side:
:):P:unsure::woohoo::huh::whistle:;):s:!::?::idea::arrow:
Please input the anti-spam code that you can read in the image.

3.26 Copyright (C) 2008 Compojoom.com / Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved."