Home / server / Questions / 196928
Accepted
polemon
Asked: 2010-11-02 06:48:12 +0800 CST

Can't connect to ESXi with vSphere Client

  • 772

after changing IPs on of the ESXi hypervisor (without setting to maintenance mode), I can't access the vCenter Server with vSphere anymore.

But I can access the ESXi over SSH. So, the IP is correct, but why can't I access it with the client?

vmware-vcenter vmware-esxi vsphere-client

4 Answers

  1. There can be several causes. Your first place to check is the VMware KB Article.

    After that...

    From root SSH on the ESXi console: 

    services.sh restart

    Or "Restart Management Network" from the F2 console.

    If you continue to see issues, do what @TCampbell said and remove/readd.

    If you are still seeing issues, RDP to your vCenter server and verify connectivity from the server to the host. Check port 901/902 from your vCenter server with telnet <ip address> <port> or another utility.

    Did your hostname change, too? You may have to regenerate SSL keys with /sbin/generate-certificates.sh

    • 3

  2. If you can't connect to it from the vSphere vCenter Server, you should remove that ESXi server from your inventory and re-add it.

    • 1

  3. Is the vCenter Server running in a virtual machine? Or are you trying to connect directly to the single vSphere on the ESXi Host? If vCenter is running in a VM, try to connect directly to vSphere on the Host that it runs on, and make sure that the VM is actually started and running properly.

    Or, when you changed IP addresses, did the vCenter Server VM change IPs too? If you changed subnets or VLANs on the host, but not the VMs themselves, maybe the vCenter VM is inaccessible to the network. In that case, connect directly to the host, use the console to connect to the VM, and fix the IP settings there.

    • 0
  4. Best Answer

    Thanks for all your answers, but the problem resolved more or less itself... The problem was, the ESXi interface throttled my connection to my IP. after a few minutes, I could access the server with vSphere, as if nothing had happened.

    • 0