Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Diagnosing the vSphere Client when it fails to connect to an ESX/ESXi host or vCenter Server (1003870)

Symptoms

  • vCenter Server cannot connect to the ESX/ESXi host.
  • Connecting vCenter Server to the ESX/ESXi host fails.
  • vSphere Client cannot connect to the ESX/ESXi host.
  • You see one or more of these errors:

    • Login failed
    • Login failed due to a bad username or password
    • Cannot complete due login due to an incorrect username or password
    • Timed out waiting for server response
    • Failed To Connect to host

Purpose

This article provides steps to troubleshoot issues when you are unable to connect to an ESX/ESXi host from the vSphere Client. The article aims to help you eliminate the common causes for your problem by verifying network connectivity, authentication, and permissions.

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document. To eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

Note: If you perform a corrective action in any of the following steps, attempt reconnecting to ESX/ESXi host with the vSphere Client.

  1. Verify that you are connecting to the correct hostname or IP address for your vCenter Server. Connections failed because incorrect server information may make the problem seem more complex than it is. Correct any incorrect names, and try connecting to vCenter Server with the vSphere Client. If the connection fails using the hostname but succeeds with IP address then it is probably a DNS error that needs to be corrected.

  2. Verify that network connectivity exists from the Client workstation to the ESX/ESXi host. For more information, see Testing network connectivity with the ping command (1003486).

  3. Verify that the ESX/ESXi Server Management service on the ESX/ESXi host is running. For more information, see Verifying that the Management Service is running on an ESX host (1003494) and Restarting the Management agents on an ESXi or ESX host (1003490).

  4. Verify that you can connect from the vCenter Server to the ESX/ESXi host on port 902 (If the ESX host was upgraded from version 2.x and you cannot connect on port 902, verify that you can connect on port 905). By default ESX/ESXi listens on port 902 and therefore if the previous steps are all correct it most means that a physical firewall is blocking connectivity on port 902. For more information, see Testing port connectivity with Telnet (1003487).

  5. Verify that the you are connecting with the correct username and password. Often, an incorrect username or password has been specified causing the log on failure to occur with the error: Cannot complete login due to an incorrect user name or password.

  6. Verify that the configured permissions for the account are sufficient to allow you to log in to the ESX/ESXi host. For more information, see Troubleshooting permissions errors when connecting to an ESX/ESXi host with the vSphere/Virtual Infrastructure client (1003887).

Note: If your problem still exists after trying the steps in this article, please:

Additional Information

See Also

Update History

06/22/2012 - Added 5.x to product versions.

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.

Feedback

  • 17 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 17 Ratings
Actions
KB: