I have the following issue when connecting to a server from the central management/licensing server.
"Unable to access the specified host. It either does not exist, the server software is not responding, or there is a network problem."
I can use the Infrastructure client to connect to it directly.
The status is right circle green but disconnected. The server is licensed.
I can connecto to 3 other ESX servers on the same subnet from the management console.
Any ideas please?
Hi, thx for esponse.
I can ping it via IP, Netbios & dns name.
I restarted service, no luck.
I removed it and re added it no luck.
I removed it, restarted service then readded and no luck.
I does find it on connect, it also finds server type and build and lets me add it to the end.
It is when it does it's read of deeper settings with the status % bar down below that it fails.
All NICs are set to auto.
All NICS are setup identical to the other 3 ESX hosts that work.
if virtual center works with other esx servers it can not be up to VC, it must be up to esx server.
you restart host agent for management, you can try restart esx .....
when you add esx to VC it creates vpxa user on esx, you can remove that user from esx and than try to add esx again to VC and new vpxa user will be automaticly recreated.
1) Delete the ESX object in VC
2) Log with SSH on ESX server
3) Delete VPXuser Account (userdel -r vpxuser)
4) Restart Management services (serivces mgmt-vmware restart)
5) Go back on VC
6) Add the ESX host again
or you can manually reinstall the VC agent
Hi sorry, but this didn't work.
I should mention that this server was 3.01 and now its 3.02
when it was 3.01 it worked. we removed it, upgrded it and now it wont connect.
Does that help at all?
When you initially add the ESX server, does it show as normal/connected for a few seconds before becoming disconnected?
If so, check that the VirtualCenter server can receive data on UDP 902 from the ESX server.
This can be confirmed by running packet capturing software, such as wireshark, on the VC server.
Are your disks full or near full? Run the following command from the ESX server: