vSphere client could not connect to esxi

[gepard_x]

vSphere client could not connect to esxi

Error message:

vmware vsphere client could not connect to "192.x.x.x". An unknown connection error occurred.

(The request failed because the remote server took too long to respond. (The operation has timed out))

Description:

Suddenly, after reboot windows station, vSphere client stopped working.

I have several esxi and each of them suddenly could not connect in vsphere client.

Restart esxi not solved this problem.

Login locally on esxi works correctly,

Enable and connect by ssh to esxi is also ok,

Connect to server esxi in vmware workstation is also ok.

Web access UI - Login and work ok.

I would like get vsphere client back to work.

Wireshark captures following packets:

vmware vsphere client - Login

- vsphere.client -> esxi / TCP / 55555 -> 443 / [SYN]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [SYN, ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [ACK]

30 second wait

- esxi -> vsphere.client / TCP / 443 -> 55555 / [FIN, ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [FIN, ACK]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [ACK]

Display error message.

Alternatively

- vsphere.client -> esxi / TCP / 55555 -> 443 / [SYN]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [SYN, ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [ACK]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [FIN, ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [ACK]

- vsphere.client -> esxi / TLSv1 / Client Hello

- esxi -> vsphere.client / TCP / 443 -> 55555 / [RST]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [SYN]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [SYN, ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [FIN, ACK]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [ACK]

- esxi -> vsphere.client / TCP / 443 -> 55555 / [FIN, ACK]

- vsphere.client -> esxi / TCP / 55555 -> 443 / [ACK]

Thank you for any response.

g.

[pwolf]

What version of ESXi hosts are affected?

Can you connect via other means (http or web console, ssh )?

[SureshKumarMuth]

have you tried this ?

vSphere Client will time out before authentication to ESXi is complete (2072539) | VMware KB

[gepard_x]

Thank you for answers

ssh - connection is working

web - Open the VMware Host Client on https://192.x.x.x/ui/#/login is working to

Version: 2016.03.02

Branch: vsphere60u2

I have esxi 5.1 and esxi 6.0

Both I can correctly connect also in vmware workstation (version 11.1.4), File->connect_to_server.

Authenticating users are two (and may some default build-in vmware users)

esxi are standalone servers (not connected to domain)

esxi don't have FQDN, just IP

As the link sad:

I set "CLIENT_CMD_TIMEOUT" to value 360 and after one minute it displayed the same error message.

Should I increase timeout value also somewhere on esxi?

g.

[admin]

Try restarting your management's networks from dcui.. if you can connect esxi from ssh or power CLI..

Another thing to check is that.. Verify the management network which was configured for your host . ..

Worst case put your host on maintance mode and try a reboot .

Let me the results.. Please paste the vmkernel.log files to check the additional error

[gepard_x]

I tried this:

Restart management network didn't solve problem

Restart esxi didn't solve problem

How to: Verify the management network which was configured for your host ?

I have: vSwitch0, vmk0(with IPv4), vmnic0(with mac), ping esxi is ok, ssh to esxi is ok.

Default TCP/IP stack (with IPv4 gw and ipv4 dns)

Port groups (vm network and management network) in vSwitch0, vlan 0

Maybe firewall rules?

But it is suddenly on all esxi's

Which TCP port vmware vsphere client use? (seemd to be 443)

In the past I had the same problem, once, on one esxi 6.0 and I solved it by restart esxi 6.0

Here is log from experimental new instalation of esxi 6.0 in VM.

[pwolf · Accepted solution]

I think, that your problem is on the workstation side. Have you tried to install the client on another machine and access the hosts from this other machine?

[gepard_x]

Thank you for recommendation, installation vsphere client on a new windows machine solved the problem, on the new machine I can connect to esxi.