In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
Solved
vSphere Connection Error
Posted on 2013-01-26
I can't connect to an ESXi 5.0 update1 host via the sphere client. I can connect to vCenter with no problems, and I can RDP into the VMs on the host with no problems. I can ping the host using the DNS name or the IP address, i can access the host via DCUI, but when I try to connect to the host via the sphere client I get the following error.
I as a result i can't add this host to vCenter either. I reset the host management agents, the management network also. I ran network test in the host's DCU and everything thing came back "Ok" with the DNS, Gateway, and Hostname. This issue started today, when there was a network issue and I believe the host became isolated (disconnected) and it's VM (disconnected), so I removed the host from vCenter and logged into the host via DCUI and reset the agents. The host and VMs were now pingable, but I can no longer access this host via the vsphere client nor can I add it to vCenter. Nothing changed in our network. I didn't try to reset this host since the VMs where running fine. I need to get this host back into vCenter so does any one have any ideas on fixing this? Thanks
I as a result i can't add this host to vCenter either. I reset the host management agents, the management network also. I ran network test in the host's DCU and everything thing came back "Ok" with the DNS, Gateway, and Hostname. This issue started today, when there was a network issue and I believe the host became isolated (disconnected) and it's VM (disconnected), so I removed the host from vCenter and logged into the host via DCUI and reset the agents. The host and VMs were now pingable, but I can no longer access this host via the vsphere client nor can I add it to vCenter. Nothing changed in our network. I didn't try to reset this host since the VMs where running fine. I need to get this host back into vCenter so does any one have any ideas on fixing this? Thanks
3
2-
2
7 Comments
Active today
telnet to the following ports
telnet 172.16.3.8 80
telnet 172.16.3.8 443
telnet 172.16.3.8 902
also try
http://172.16.3.8
do they connect?
are you using the same IP Address which is displayed on the DCUI (console screen).
perform the above from a workstation and the vCenter Server.
telnet 172.16.3.8 80
telnet 172.16.3.8 443
telnet 172.16.3.8 902
also try
http://172.16.3.8
do they connect?
are you using the same IP Address which is displayed on the DCUI (console screen).
perform the above from a workstation and the vCenter Server.
Active today
IanTh
Yes the management port is the same and has not changed.
hanccocka
yes https://172.16.3.8 does connect, but I cannot telnet into 80 or 443.
When I telnet into 902 I get this message:
Port 80 and 443 give absolutely no response, but the image is the response of 902
Yes the management port is the same and has not changed.
hanccocka
yes https://172.16.3.8 does connect, but I cannot telnet into 80 or 443.
When I telnet into 902 I get this message:
Port 80 and 443 give absolutely no response, but the image is the response of 902
Active today
if http (port 80) connects and you get a web page - response is okay.
902 - that is the correct response.
check any firewalls, of group policys that have been defined, that block 443. Recently we had an issue where a vCenter Server had been moved to different AD OU, which had a firewall policy which cause this issue.
Port 443 is the port which the vSphere Client connects on.
Restart the Hosts.
902 - that is the correct response.
check any firewalls, of group policys that have been defined, that block 443. Recently we had an issue where a vCenter Server had been moved to different AD OU, which had a firewall policy which cause this issue.
Port 443 is the port which the vSphere Client connects on.
Restart the Hosts.
Active today
Strangely enough. I started working again. I didn't do anything, also of a sudden, i could connect via the vsphere client. I just joined it back to vCenter also with no problems. That was really strange, but thanks for you replies.
Featured Post
In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
August and September have been big months for VMware—from VMworld last month to our new Course of the Month in VMware Professional - Data Center Virtualization. We reached out to Andrew Hancock, resident VMware vExpert, to have a more in-depth discu…
Herein one will find an aggregate of some of my experience building and deploying virtualization stacks both in standalone, clustered Hyper-V, clustered Hyper-V with a Scale-Out File Server (SOFS) backend, and Storage Spaces Direct (S2D).
- Virtualization
- Windows 10
- Windows Server 2016
- Hyper-V
- Windows
- Azure, *Clustering
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Suggested Courses
Course of the Month4 days, 20 hours left to enroll
580 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.