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

Unable to connect to an ESX host using Secure Shell (SSH) (1003807)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 29995Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

You are unable to connect to an ESX host using SSH.

You receive one or more of these errors when trying to connect:

Network error: Connection refused.

Error code: 24577 (0x6001)

Error code: 110 (0x006E)

Purpose

This document guides you through the process of troubleshooting an SSH connection to an ESX host.

Note: This article applies only to ESX 4.x and earlier versions. In ESXi 4.1 and later, VMware recommends that you use Tech Support Mode. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.0 (1017910).

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order 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.

Verify that there is network connectivity between the SSH client and the ESX host. For more information, see Testing network connectivity with the Ping command (1003486) .

Verify that port 22 on the ESX host can be reached from the SSH client machine. For more information, see Testing port connectivity with the Telnet command (1003487).

Verify that the username and password is correct by logging directly in to the console. A common error is to use an incorrect username or password, which causes a login failure and an access denied error message to appear.

Verify that the SSH Daemon is running. For more information, see Verifying that the Secure Shell Daemon is running on an ESX host (1003906).

Verify that user is permitted to access the host via SSH. For more information, see Enabling root SSH login on an ESX host (8375637).

Verify that the ESX host firewall permits SSH connections. For more information, see Configuring the ESX host firewall for SSH (1003808).

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

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 Knowledge Base article ID (1003807) in the problem description. For more information, see How to Submit a Support Request.

Related Information

Note: To enable SSH access for local user accounts created on ESX 4.1, see Local users created on ESX and ESXi 4.1 systems cannot log in (1024235).

Testing network connectivity with the ping command
Testing port connectivity with Telnet
Collecting diagnostic information in a VMware Virtual Infrastructure Environment
Configuring the ESX host firewall for SSH
Verifying that the Secure Shell Daemon is running on an ESX host
Using Tech Support Mode in ESXi 4.1, ESXi 5.x, and ESXi 6.x
Local or Active Directory Domain users on ESX and ESXi 4.1 systems cannot log in
Não é possível conectar a um host ESX usando o Secure Shell (SSH)
无法使用 Secure Shell (SSH) 连接到 ESX 主机
无法使用 Secure Shell (SSH) 连接到 ESX 主机
No es posible conectarse a un host ESX mediante Secure Shell (SSH)
セキュア シェル (SSH) を使用して ESX ホストへ接続できない
HBA の proc 情報を使用して、ファイバチャネルの接続に関する問題判別をする方法
多数のデータストアがある環境でステートレス キャッシュが有効化されていると、ホスト プロファイルのコンプライアンス チェックがタイムアウトする
Enabling root SSH login on an ESX host

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

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