Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 29104Language:
Chinese (Simplified)JapaneseEnglish

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

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.

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 network connectivity exists from the Client workstation to the ESX/ESXi host. For more information, see Testing network connectivity with the ping command (1003486).

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).

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.

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:

Gather the 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 KB Article ID in the problem description. For more information, see How to Submit a Support Request.

Related Information

For more information, see:

vCenter Server displays the error: Failed to connect to host (1010837)

An ESX/ESXi 3.x or 4.x host takes a long time to boot when the DNS servers are unreachable (1023866)

Cannot connect to the ESX/ESXi host or add it to vCenter Server (1030895)

Testing network connectivity with the ping command
Testing port connectivity with Telnet
Restarting the Management agents in ESXi
Verifying that the Management Service is running on an ESX host
Collecting diagnostic information in a VMware Virtual Infrastructure Environment
Troubleshooting permissions errors when connecting to an ESXi/ESX host with the vSphere Client
VMware vCenter Server displays the error: Failed to connect to host
An ESX/ESXi 3.x or 4.x host takes a long time to boot when the DNS servers are unreachable
Cannot connect to the ESX/ESXi host or add it to vCenter Server
ESX/ESXi ホストまたは vCenter Server への接続に失敗したときの vSphere Client の診断
当 vSphere Client 连接 ESX/ESXi 主机或 vCenter Server 失败时对其进行诊断

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Verificação da integridade de arquivo da máquina virtual hospedada (1003846)

KB
•
验证托管虚拟机的可用磁盘空间是否充足 (1003856)

KB
•
Como localizar os arquivos de uma máquina virtual hospedada (1003880)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant