vSphere Client could not connect to vcenter

[Dreher]

Friends,

I can not connect with the vCenter, the message is:

vSphere Client could not connect to vcenter. 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.))

vCenter is 5.5 Update 2.

[schepp]

Hi,

ok, so first let's check the obvious things: network connectivity. Can you ping the vCenter server, might a firewall be in place?

Then move forward to the vCenter Server. Is the vCenter service running?

If yes how is the usage of the vCenter server? Is it permanently at 100% CPU? Connections might fail then.

Tim

[Dreher]

Ok,

- Firewall is disabled;

- vSphere Client is installed in localhost (vCenter), is same server !!!

- Resources (CPU/Memória) is available;

[sadiq1435]

Since Vmware 5.5 vsphere web client is the only client to connect to vCenter Server . Vsphere Client is not supported .

[rcporto]

Sorry brother, but this is not true... in version 5.5 you can still use the vSphere Client to connect to vCenter.

And Dreher, can you confirm the operating system where you're running the vSphere Client ?

[schepp]

So what server IP / Name do you put in the vSphere client? Tried with localhost, IP and dns name?

Please check if the vCenter service is running in the windows services!

Tim

[hasaanB]

not saying this is your problem... but have a look at this as well since we were running into same error.

https://communities.vmware.com/message/2385653

[Dreher]

Richardson,

The operating system is windows server 2008.

[herwonowr]

As what was said by Tim Scheppeit , is the vCenter service running or not?

[bhards4]

Hi,

ESXi 5.5 has degraded viclient to access vcenter or esxi.

Thats also true that in esxi5.5 u2, there is a provision to use VI Client  through c#.

If you are using 5.5 U2 then obviously you can use viclient, only thing it will popup warning message.

Main thing , pls check vCenter services status . Also have a look into vSphere 5.5 Client and WindowsXP/Windows2003 – Unknown Connection Error « Mike L...

Regards,

Bhards4

[keshavp]

I see the same connection issue on Windows XP (I know it's old/deprecated) but I wonder if it is the problem..

I'm running vCenter 6.0. vSphere client is 5.1 (I'm told that they are compatible).

Here's what I see in the logs (Complete log is attached). Would someone be able to decrypt that for me please? Many Thanks in advance.

Network connectivity between the client and vCenter server is fine. I see the CPU usage is about 17%. 

[        :Failed t:P: 3] 2015-10-09 13:40:57.168  System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.

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

[        :Error   :P: 3] 2015-10-09 13:40:57.168  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.)

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

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

...

[        :Error   :M: 1] 2015-10-09 13:40:57.355  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.)

and where is clients.xml located?

[keshavp]

I think the issue is with Windows XP. I am able to login successfully on Windows 7.

[santosh90]

Dear sir ,

   I am using VMware Esxi7 i am facing same issue. i am getting ping but unable to access through web client