book
Article ID: 308932
calendar_today
Updated On:
Environment
VMware ESXi 4.0.x Embedded
VMware ESX 4.1.x
VMware vSphere ESXi 5.1
VMware ESXi 3.5.x Embedded
VMware ESXi 4.0.x Installable
VMware ESX 4.0.x
VMware vSphere ESXi 5.0
VMware ESX Server 3.5.x
VMware ESX Server 3.0.x
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 5.5
VMware ESXi 3.5.x Installable
VMware ESXi 4.1.x Installable
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.
-
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.
-
-
-
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).
-
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.
-
Note: If your problem still exists after trying the steps in this article, please:
-
-
File a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request.