CaptPetecard
Contributor
Contributor

"Could Not Connect" using VSphere to ESXi 5.0 until reboot

Please provide ideas on solving recurring VSphere lockouts.


Symptoms:

-I am locked out of an ESXi 5.0 host using VSphere until I reboot the host.

-The guest VM's are accessible via RDP and run fine.

-After a day or two, the hypervisor host locks VSphere out again.

-I can only access the system via DCUI when locked out. Restarting network services via DCUI does not work. The diagnostic test fails its ping tests.

Here is the VSphere error I am getting connecting to ESXi 5.0:

---------------------------

Could Not Connect

---------------------------

vSphere Client could not connect to "myserver.somewhere".

An unknown connection error occurred. (The client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.))

---------------------------

OK  

---------------------------

When locked out, Chrome browser navigation to: https://myserver.somewhere gives:

This webpage is not available

The connection to myserver.somewhere was interrupted.

Check your Internet connection

Check any cables and reboot any routers, modems, or other network devices you may be using.

Allow Chrome to access the network in your firewall or antivirus settings.

If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.

If you use a proxy server...

Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect "Use a proxy server for your LAN".

Error code: ERR_CONNECTION_RESET

When I navigate Chrome to another ESXi 5.0 host box, I successfully get the VMware ESXi Welcome page, which tells me it is not a Windows VSphere client issue.

I do not have logs to give you, as I am not at the DCUI.

Others apparently have this problem in various versions of ESXi. I have yet to find a relevant solution after a Google and VMware forum search.

Thank you for your assistance.

-P

0 Kudos
2 Replies
jonathanp
Expert
Expert

0 Kudos
CaptPetecard
Contributor
Contributor

jonathanp

I went another route. Thanks for your suggestion regardless.

I went with was tightening up security. So far this has worked.

-P

0 Kudos