VMware Cloud Community
55jbosco
Contributor
Contributor

can't connect to esxi host via vsphere client

Hello,

I'm getting the error message below when i try to connect to esxi hosts.

"A communication error occurred while sending data to the server. (the underlying connection was closed: an unexpected error occurred on a send)"

I have two esxi hosts and i have this problem on both. I can ping them but i can't connect. There is no firewall between hosts and clients. After i restart the hosts, i can connect, but after a couple of days the problem occurres again.

Version informations are below:

ESXI 4.1.0 Build 348481

Vsphere client 4.1.0 Build 345043

Do you guys have any idea about this problem?

Thanks in advance.

Reply
0 Kudos
17 Replies
LuigiC
Enthusiast
Enthusiast

I see this as being fixed in the release notes of esxi 4.1 update 2

ESXi host configured with vNetwork Distributed Switch (vDS) disconnects from the vCenter Server and does not reconnect even after multiple attempts
The portset global lock is present for port enable, but not for port disable. When port disable modifies vDS properties, it conflicts with other port states that are modifying vDS properties. As a result of the conflict, the network connection is lost and the ESXi host disconnects from the vCenter Server. Also, a Limit exceeded error message appears in the VMkernel log.

Reply
0 Kudos
55jbosco
Contributor
Contributor

i don't have vcenter. im using vshpere client to connect to standalone esxi hosts. and i have 2 more hosts with the same version and i don't have this problem on them 😕

Reply
0 Kudos
onoski
Enthusiast
Enthusiast

Have a read through this previous post with similar issues: http://communities.vmware.com/message/1634735

Reply
0 Kudos
Sawkat
Contributor
Contributor

check your logs and see whats in there... via the console (via the unsupported command line Smiley Happy )

Reply
0 Kudos
55jbosco
Contributor
Contributor

already read these threads but i have no firewall between client and hosts.

Reply
0 Kudos
Sawkat
Contributor
Contributor

try accessing the hosts via the web : http://ip. If does not work then restart the management services via the console

Reply
0 Kudos
55jbosco
Contributor
Contributor

i can't access via web. i already tried to restart management services but it doesn't change anything. only reboot is the only solution in this case but like i said it happens again in a couple of days after reboot.

Reply
0 Kudos
Sawkat
Contributor
Contributor

i would create another vmk definitely not to lose time, another test I would do is when this happens I would try to ping another machine on the same segment from the console of the host

Reply
0 Kudos
55jbosco
Contributor
Contributor

i can ping other computers on the same segment from console of the hosts.

2 vmk on a host is not harmful, right? Smiley Happy i will try this..

Reply
0 Kudos
Sawkat
Contributor
Contributor

:smileygrin: might be a gateway issue there Smiley Wink

check your gateways and route

Reply
0 Kudos
55jbosco
Contributor
Contributor

client and hosts are on the same switch and subnet.

Reply
0 Kudos
Sawkat
Contributor
Contributor

I mean check the gateways you set on your vmk's Smiley Wink

Reply
0 Kudos
LuigiC
Enthusiast
Enthusiast

The client connects to the ESX host in the same way that vcenter would (it would have the same issue).

Also you should check you Nic firmware and drivers, You haven't told me any of that information so I really can't help with it.

Reply
0 Kudos
55jbosco
Contributor
Contributor

nic is Broadcom NetXtreme II BCM5709 1000Base-T and server is IBM X3650 M3 7945KFG

Reply
0 Kudos
Adejumo
Contributor
Contributor

Hi  please i am having the same problem connecting with vspere client 

is it very critical that one downloads the vsphere client with the static IP ADDRESS set during installation    ? 

Reply
0 Kudos
ScholesyTH
Contributor
Contributor

I have problem same your and still did not found a solution.

Hosts inside still working fine ( i can remote directly by remote desktop or teamviewer),

and services inside host working well.

Problem just cannot login by vsphere client.

If I restart ESXi, I can login again.

I see some issue before this problem in system log, It like root@127.0.0.1 login fail many times.

I think it maybe attack from someone but nobody use login at server at that time.

If someone can help me please tell.

Reply
0 Kudos
MisterPickles
Contributor
Contributor

I had a similar issue and just on a hunch I tried running the VSPhere Client as administrator, and it worked!  Right click the icon and choose "Run As Administrator."

Reply
0 Kudos