Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Diagnosing an ESXi/ESX host that is disconnected or not responding in vCenter Server (1003409)
Symptoms
- An ESXi/ESX host shows as Not Responding in VirtualCenter / vCenter Server
- An ESXi/ESX host shows as Disconnected in vCenter Server
- You cannot connect an ESXi/ESX host to vCenter Server
- Virtual machines on an ESXi/ESX host show as grayed out in vCenter Server
- When attempting to add an ESXi/ESX host to vCenter Server, you see an error similar to:
Unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem
Purpose
Resolution
ESXi
- Verify that the ESXi host is in a powered on state.
- Verify that the ESXi host can be reconnected, or if reconnecting the ESXi host resolves the issue. For more information, see Changing an ESXi or ESX host's connection status in vCenter Server (1003480).
- Verify that the ESXi host is able to respond back to vCenter Server at the correct IP address. If vCenter Server does not receive heartbeats from the ESXi host, it goes into a not responding state. To verify if the correct Managed IP Address is set, see Verifying the vCenter Server Managed IP Address (1008030) and ESXi 5.0 hosts are marked as Not Responding 60 seconds after being added to vCenter Server (2020100). See also, ESXi/ESX host disconnects from vCenter Server after adding or connecting it to the inventory (2040630)
- Verify that network connectivity exists from vCenter Server to the ESXi host. For more information, see Testing network connectivity with the ping command (1003486).
- Verify that you can connect from vCenter Server to the ESXi host on TCP/UDP port 902. If the host was upgraded from version 2.x and you cannot connect on port 902, then verify that you can connect on port 905. For more information, see Testing port connectivity with Telnet (1003487).
- Verify if restarting the ESXi Management Agents resolves the issue. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).
- ESXi hosts can disconnect from vCenter Server due to underlying storage issues. To investigate further, see Identifying Fibre Channel, iSCSI, and NFS storage issues on ESXi/ESX hosts (1003659).
ESX
- Verify that the ESX host is in a powered on state.
- Verify that the ESX host can be reconnected, or if reconnecting the ESX host resolves the issue. For more information, see Changing an ESXi or ESX host's connection status in vCenter Server (1003480).
- Verify that the ESX host is able to respond back to vCenter Server at the correct IP address. If vCenter Server does not receive heartbeats from the ESX host, it goes into a not responding state. To verify if the correct Managed IP Address is set, see Verifying the vCenter Server Managed IP Address (1008030). See also, ESXi/ESX host disconnects from vCenter Server after adding or connecting it to the inventory (2040630)
- Verify that network connectivity exists from vCenter Server to the ESX host. For more information, see Testing network connectivity with the ping command (1003486).
- Verify that you can connect from vCenter Server to the ESX host on TCP/UDP port 902. If the ESX host was upgraded from version 2.x and you cannot connect on port 902, then verify that you can connect on port 905. For more information, see Testing port connectivity with Telnet (1003487).
- Verify that the ESX management service
vmware-hostdis running. For more information, see Verifying that the Management Service is running on an ESX host (1003494) and Troubleshooting vmware-hostd service if it fails or stops responding on an ESXi/ESX host (1002849).
- Verify that the VirtualCenter agent service
vmware-vpxais running. For more information, see Verifying that the vCenter Server Agent Service is running on an ESX host (1003495).
- Verify that the
xinetdservice is running. Ifxinetdis not running, authentication may fail. For more information, see Determining if the xinetd service is running on an ESX host (1007323).
- Verify if restarting the ESX Management Agents resolves the issue. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).
- Verify that no processes are over-utilizing the resources on the Service Console. For more information, see Checking for resource starvation of the ESX Service Console (1003496).
- ESX hosts can disconnect from vCenter Server due to underlying storage issues. To investigate further, see Identifying Fibre Channel, iSCSI, and NFS storage issues on ESXi/ESX hosts (1003659).
Note: If your problem still exists after trying the steps in this article:
- Gather VMware Support Script Data. For more information, see Collecting diagnostic information in a VMware Virtual Infrastructure Environment (1003689).
- File a support request with VMware Support and note this Knowledge Base article ID (1003409) in the problem description. For more information, see How to Submit a Support Request.
Additional Information
For translated versions of this article, see:
Tags
See Also
- Troubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi host
- Changing an ESXi or ESX host's connection status in vCenter Server
- Testing network connectivity with the ping command
- Testing port connectivity with Telnet
- Restarting the Management agents on an ESXi or ESX host
- Verifying that the Management Service is running on an ESX host
- Verifying that the vCenter Server Agent Service is running on an ESX host
- Checking for resource starvation of the ESX Service Console
- Identifying Fibre Channel, iSCSI, and NFS storage issues on ESX/ESXi hosts
- Collecting diagnostic information in a VMware Virtual Infrastructure Environment
- Determining if the xinetd service is running on an ESX host
- Verifying the vCenter Server Managed IP Address
- All ESX hosts simultaneously show a status of Not Responding in vCenter
- TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components
- Diagnósticando un host ESX o ESXi que se desconecta o no responde en vCenter Server
- vCenter Serverから切断、又は無応答となっているESX・ESXiホストの診断方法
- ESXi 5.0 hosts are marked as Not Responding 60 seconds after being added to vCenter Server
- Diagnosticar no vCenter Server um host do ESX ou ESXi que esteja desconectado ou não esteja respondendo
- ESXi/ESX host disconnects from vCenter Server after adding or connecting it to the inventory
- 诊断在 vCenter Server 中已断开或无响应的 ESXi/ESX 主机
Update History
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

