VMware Cloud Community
Cruicer
Enthusiast
Enthusiast
‎03-25-2009 11:58 AM

Unable to contact the specified host (Servername). This might be because that host is not available....

I am getting the following error

"Unable to contact the specified host (SERVERNAME). This might be because the host is not available on the network, there's a network configuration problem, or the Management services on the host are not responding.

ESX host is a 3.0.2 build 52542. Virtual Center is running 2.5 update 4...Update 4 was just applied over the weekend.

What I have tried so far:

I can ping the VC server from the host having the issue by short name, FQDN and IP and vica-versa

  • Stopped and restarted the vmware-vpxa agent as well as the mgmt-vmware agent

  • Rebooted the host

  • Restarted Virtual Center.

  • Installed the upgrade VPXA agent locally on the host (Vmware-vpxa-2.5.0-147697)

  • Removed the host from VC tried to add it back in

  • Plenty of diskspace.

None of this is working for me. This just happened, as I said, we applied Update 4 over the weekend. A colleague of mine was simply trying to register a VM to this host, and it went disconnect.

Ideas...suggestions, up to about 3 hours ago it was FINE!

0 Kudos
4 Replies
weinstein5
Immortal
Immortal
‎03-25-2009 06:15 PM

Can you ping the host from the VC Server?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
ehawk01
Contributor
Contributor
‎04-09-2009 07:33 AM

Was there a resolution to this problem. We are seeing the same thing.

0 Kudos
Cruicer
Enthusiast
Enthusiast
‎04-09-2009 09:23 AM

No not really...I have VMware tech on the phone for about an hour. we tried a bunch of things...the last thing we did before he was going to esculated was try to add into VC. And surprise it just went in. how I have been having the same issue here and there on new hosts and am finding that if I simply try to add it and it fails to just let it sit for about 1/2 hour, then try again...9 out of 10 times that works...not much help there but...

0 Kudos
Xeroloper
Contributor
Contributor
‎04-22-2009 09:27 AM

I was recieving the same error and discovered that I didn't have file and printer sharing enabled and set as an exeption in the firewall. Once that was set I was able to continue normally. That may not be your situation but I hope that it may help others like me who's search ends up here.

0 Kudos