"unable to access the specified host, It either does not exist, the server software is not responding, or there is a network problem"
Ive got a VC server with no firewall in between it and the esx hosts (all of them are showing disconnected)and all on the same segment, If i telnet to to the esx host from the windows box using telnet servername 902 it connects ok. But if i try to add the host it fails with the message above.
Ive verified there is no additional file backed up in /etc/vmware/firewall which can cause this issue.
If i try to add the host with an incorrect user and pass, it actually tells me that the password is incorrect, if i try adding using the root account i get the error above.
Windows firewall is disabled on the VC server
esxcfg-vswif -l gives me output showing the correct IP bound to vswif0
Name Port Group IP Address Netmask Broadcast Enabled DHCP
vswif0 Service Console 192.168.0.21 255.255.255.0 192.168.0.255 true false
Anyone have an suggestions on what i should check next ?
Are you trying to connect via IP address or host name? Since our virtual environment is not communicating with our DNS server, we had to create hosts files on the VC server before we could connect using the host name.
Thanks for the reply guys, i was trying to add it by its IP address, any ideas why the existing hosts that were already added suddenly became disconnected and why these can not be added again ? Ill do some nslookups and add an entry in the host file and see if that does anything
Hi. Yes all communication tests are ok, PING, NSLOOKUPS, I can telnet to port 902 of the esx hosts from the VC server
The virtual Client can not connect directly to the esx hosts either.
I can however SSH via putty.
Ive tried connecting via DNS, IP
Ive also configured --allowIncoming and --allowOutgoing on the firewall of the esx host
One strange thing also, is i can not browse to the web interface on the esx hosts.
I enabled extended verbose logging on the VC server and here is the output from the log file.. any ideas ?
\[2006-11-22 19:09:23.622 'App' 2888 verbose] \[VpxdHostAccess] Attempting to connect to host agent on
\[2006-11-22 19:09:24.059 'VpxdProfiler' 2888 verbose] counter name: /vpxd/methodStats/vim.Datacenter.queryConnectionInfo/TotalTime
then run ps -ef | grep vpxa
There should be nothing in the process list.
then run /etc/init.d/vmware-vpxa start
then run ps -ef | grep vpxa
You should see the vpxa in the process list.
Try using the VI client to connect to the host directly.
let me know.
\[root@******* init.d]# ./vmware-vpxa stop
\[root@******* init.d]# ps -ef | grep vpxa
root 19824 19768 0 05:33 pts/0 00:00:00 grep vpxa
\[root@******* init.d]# ./vmware-vpxa start
[root@******* ps-ef | grep vpxa
root 19839 1 0 05:34 pts/0 00:00:00 /bin/sh /usr/bin/vmware-watchdog -s vpxa -u 30 -q 5 /usr/sbin/vpxa
root 19844 19839 0 05:34 ? 00:00:00 /usr/lib/vmware/vpx/vpxa
root 19857 19768 0 05:34 pts/0 00:00:00 grep vpxa
when i try to connect via VC it gives the unable to connect error, if i use the vc client to connect directly to the host it gives "Connection failed"
Then there are 2 possible causes for this.
#1 Either the port that vpxa is listening on has changed.
#2 There is a firewall that prevents the connections.
Is your VC host on the same subnet as the ESX hosts?
If you can not connect to any of your ESX hosts then the likely cause is a firewall blocking the connections.
Plug a laptop with VC Client installed on it in to the same physical switch that the ESX hosts are connected to and see if you can connect then.
Also check that the date and time on the VC and ESX hosts are in the same ballpark. SSL doesn't like it if the time on two hosts differ by oh, say, a year or so.
In the same breath, also check the time zones and DST settings of all ESX and VC hosts involved.
You could potentially run into all sorts of issues with self-signed certificates expiring or not being valid yet. But none of that is usually reported by the GUI.
i have tried everything short of rebooting the esx server, there is no firewall between servers either. when i connect to the esx box vi vc client the only thing out of the ordinary is the error i get "A general system error occured: Failed to serialize result". Any ideas would be appreciated.
I am having a very similar issue with my ESX environment right now. We had some power issues due to the high winds last week so our ESX hosts (3.0) got shut down improperly. When they came back up, they seem to be fine but in VC (2.0.1) they showed up as disconnected. I had tried to "reconnect" them and got the same unable to access the specified host error. So I removed all 3 from VC successfully and tried to add again. Same error. I also have verified that I can connect to each host using the VC Client. I also have checked my license server (on the same machine as VC) and it shows the proper amount of licenses issued. When connecting directly to the ESX host I check licensing and all looks well there also. I will keep digging in on this one......any ideas?
Add: I found this other thread that seems to be the solution. I will update if it works in my environment.
Message was edited by:
Ok I think I have narrowed it down to having the VPXUser still on all my hosts but not in the inventory of VC. I am a total Linux newb so I have no idea how to delete the VPXUser. How is this done?