VMware Cloud Community
alrchris
Contributor
Contributor
Jump to solution

vsphere client connection problem

Recently I found myself cannot connect to Esxi host at datacenter through vsphere client 5.5 by several computers (Windows 7). It shows:

          vSphere Client could not connect to "xxx.xxx.xxx.xxx".

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

All VMs resume normally. And the telnet result seems normal at port 902:

          220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported

However, if I access http://xxx.xxx.xxx.xxx:902. It showed:

          220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported

          SSL: Unknown SSL Error

          VMAuthdSocketRead: read failed. Closing socket for reading.

SSH access has not been enabled, and I can't find any way to access the Esxi host.

Anyone got an idea on the issue?

Reply
0 Kudos
1 Solution

Accepted Solutions
Shirish_Madhari
Contributor
Contributor
Jump to solution

You can try restarting management agents on the host through DCUI.

This article could help you: VMware KB: Restarting the Management agents on an ESXi or ESX host

--- If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points. Shirish Madharia VCP 5 - DCV

View solution in original post

Reply
0 Kudos
4 Replies
raog
Expert
Expert
Jump to solution

Did you try accessing the host via DCUI?

Regards

Girish

To Virtualization and beyond! PS::If you felt the answer as helpful, please mark it as helpful/answered so that it helps other users as well! Blog:: www.virtualtipsntricks.com
Shirish_Madhari
Contributor
Contributor
Jump to solution

You can try restarting management agents on the host through DCUI.

This article could help you: VMware KB: Restarting the Management agents on an ESXi or ESX host

--- If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points. Shirish Madharia VCP 5 - DCV
Reply
0 Kudos
Cyberfed27
Hot Shot
Hot Shot
Jump to solution

You may want to review the host logs (assuming you can get back into it). You've got issues with SSL certs somewhere.

Reply
0 Kudos
alrchris
Contributor
Contributor
Jump to solution

Thanks all for your reply.

I can access to ESXi host by vsphere client after restarting management agents through DCUI.

But just as Cyberfed27 said, the error remains when I access http://xxx.xxx.xxx.xxx:902 at web browser.

          SSL: Unknown SSL Error

          VMAuthdSocketRead: read failed. Closing socket for reading.

I then took a look on host log from vsphere, and found the previous errors on vsphere connection:

[        :Error   :P: 3] 2014-07-11 xx:xx:xx.xxx  possible failure processing clients.xml

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

   at VirtualInfrastructure.Utils.WebQuery.LocalizeWebException(WebException exception)

   at VirtualInfrastructure.Utils.WebQuery.Request(String url, Nullable`1 timeoutSecs)

   at VirtualInfrastructure.Utils.ClientsXml.ParseXml(Int32 timeoutSecs)

   at VpxClient.Login.ClientsXmlLoader.TrySinglePort(ClientsXml clientXml, Exception& activeError)

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.

Server stack trace:

   at System.Net.HttpWebRequest.GetResponse()

Exception rethrown at [0]:

...

   at System.Net.HttpWebRequest.GetResponse()

   at VirtualInfrastructure.Utils.WebDownload.GetResponse()

   at VirtualInfrastructure.Utils.WebDownload.get_ResponseStream()

   at VirtualInfrastructure.Utils.WebQuery.Request(String url, Nullable`1 timeoutSecs)

System.IO.IOException: Authentication failed because the remote party has closed the transport stream.

...

   at System.Net.ConnectStream.WriteHeaders(Boolean async)

   --- End of inner exception stack trace ---

   --- End of inner exception stack trace ---

[        :Error   :M: 1] 2014-07-11 xx:xx:xx.xxx  Error retrieving clients.xml

Exception already logged, summary: System.Net.WebException:The client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.)

Is that the problem of client-side SSL cert? I have no idea how and where the SSL cert has been implemented.

Reply
0 Kudos