I upgraded to VC2 -and now I can't add one of my ESX servers (that was working fine before) to VC. It's accessible because I connect to it - it prompts me for the account and password and then it displays the VM's on the server. But when I hit finish it says "Unable to access the specified host. It either does not exist, the server software is not responding or there is a network problem". I rebooted the ESX server, but that didn't help. Any ideas? thanks!
Yes, you should be able to do that. You might want to try restarting the management agent on the ESX host. Log in to the service console and run "service mgmt-vmware restart". Give it a minute to start up fully and try connecting to it directly with the UI.
Ah yes, you can only do this with ESX 3.x. Can you connect to the MUI on each host? Can you log in to the console OS and check that there is a process running vmware-ccagent or vmware-serverd?
I had the same problem. I was able to connect the ESX to VC by running the installer script manually.
I issued sh /var/run/vmware/upgrade/upgrade and finally the ESX could be connected to VC. However, this is just a test machine so I dont care if this is okay or not. I am not sure if running this script manually is sufficient and does not leave out any necessary cleanup or anything.
Has anyone resolved this issue ? I've tried everything mentioned in the threads about this and still nothing. Everytime that I try to add it to VC I get the same error "Unable to access the specified host. It either does not exist, the server software is not responding, or there is a network problem".
Anyone with suggestions or advice would be welcome. Trying to aviod rebooting this box as there are clients running on it.
I have the same erro today I was registering some virtaul machines throught the webserver and they were appearing on VC but them I lost connection somehow and I can't connect I restarted the server and nothing I have 2 ESX like that.
ESX 2.5.0 was connected and 2 days after during work it stop refreshing and lost connection (it happen today) I restarted the system and nothing.
ESX 2.5.2 never could connect
I just want to migrate machines to ESX 3.01 to re-install
We upgraded to latest and greatest 3.0.1 patches (there were a bunch released at the beginning of March 07). Rebooted, and bingo, no problem anymore.
No idea whehter the reboot or the patches (or both) actually fixed it. The problem made me think that some network services weren't functioning correctly, not listening. Restarting network services at the command line did not restore service so I'd suggest a good old-fashioned reboot.
i didnt read the whole thread, but had the same problem
my problem was resolved by making sure that the VC and the SC were both on the same vSwitch
oh im running the VC virtually for the time being anyways...
We have the same problems with our remotely connected ESX 2.5.4 servers. We have 7 of them, and all but two have gone to a disconnected state and refuse to re-connect. MUI works great, and looking at packet captures from the virtual center server does not show any signs of network issues.
We have a case open with VMWare about it as well. No response yet.
Anyone have a solution here?