VMware Cloud Community
KlBst
Contributor
Contributor

ESXi5.1 / vSphere Client: "Unable to connect to the MKS:"

I have got the same error message as in discussion 2007405:

:smileycry: "Unable to connect to the MKS: The remote host certificate has these problems:" Smiley Sad

The "problems" are not specified. The above mentioned solution to create new certificates does not help. At least not without rebooting the host.

Additionally as I am not using a vCenter Server I can not "remove the Host an re add it"

Until yesterday everything works fine. There was not reboot neither on the host nor on the running clients.

The message is the same for all running clients. The clients seem to be healthy as far as I can contact them via ssh.

What to do? ... just reboot the host?

Klaus

Reply
0 Kudos
10 Replies
KlBst
Contributor
Contributor

Still no solution:

  • created new certificates
  • host reboot -> new certificat is shown when connecting to vSphere Client

BUT: Still impossible to connect to client consoles :smileyangry:

Klaus

Reply
0 Kudos
cmc_prd
Contributor
Contributor

Hi

actually I am in the same situation now.

I have changed nothing at all and I get this error: "Unable to connect to the MKS: The remote host certificate has these problems:"


Additionaly I see this error:

W110: SSL: Unknown SSL Error

2013-07-22T14:33:34Z vmauthd[10348866]: vthread-3| I120: SSL Error: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca

2013-07-22T14:33:34Z vmauthd[10348866]: vthread-3| W110: VMAuthdSocketRead: read failed.  Closing socket for reading.

What could be wrong?

I use only vSphere Client with no vCenter.

Any clues?

Reply
0 Kudos
virtualhs
Contributor
Contributor

I've got the same problem since last week. Changing the cetrificate doesn't solve the problem.

Is there a solution known?

Thanks!

Reply
0 Kudos
El_Santos
Contributor
Contributor

Does any body have an update??

Was anyone actually able to solve this?

This is mighty annoying, and VMWare has not piped up about this at all...

Reply
0 Kudos
El_Santos
Contributor
Contributor

I attempted to use this VMWare KB Article, which had no effect:

Opening the virtual machine console after a fresh installation of ESXi or ESX fails with the error: The host certificate chain is not complete (2006124)

Reply
0 Kudos
El_Santos
Contributor
Contributor

I had this issue on 2 different servers.

I was able to work around this in one of the servers by enabling the Virtual Console over VNC.

These 2 references proved very useful.  I hope this helps anyone else out there:

http://bitsmarts.blogspot.ca/2013/01/enable-vnc-in-vmware-esxi-51.html
http://robertbchase.blogspot.ca/2009/12/video-console-on-esxi-vm-without-using.html
Reply
0 Kudos
CedricAnto
VMware Employee
VMware Employee

Are you able to telnet to ESX host on port 902 ?

MKS=Mouse Keyboard Screen, these components activities are rendered over the network through port 902 from host to client machine.

Certificate error may be misleading, if it is indeed a certificate error or corruption, you can simply ssh to the ESX host as root and run sh /sbin/generate-certificates.sh. This should fix it.

Cedric http://in.linkedin.com/in/cedricrajendran/ http://virtualknightz.com/
Reply
0 Kudos
Vishalthom
Contributor
Contributor

Hi , Even i faced same problem today.

While installing OS on new VM the error was flashing "Unable to connect to the MKS: The remote host certificate has these problems"

I follow below steps to resolve this issue.

1. Restart host.

2. Disconnect and reconnect host from vcenter.

I suspect the problem is with host certificate. 

Reply
0 Kudos
impranayk
Enthusiast
Enthusiast

Did you try below KB article?

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100675...

Is it showing in all host or any specific host?

if not in all host then did you try migrating VM to other working host? Did this resolve the issue?

If other host doesn't have same issue in cluster/VC, then i would suggest to remove particular ESXi host from VC and readd it back

Regards,

Pranay(VCAP5-DCA, VCAP5-DCD)

-------------------------------------------------------------------------
Follow me @ www.vmwareinsight.com
Please consider marking this answer "correct" or "helpful" if you found it useful

Pranay Jha | Blog: http://vmwareinsight.com
vExpert 2016/2017, VCAP5-DCD/DCA, VCP5-DCV, VCA-Cloud, VCE-CIA, MCSE, MCITP
Reply
0 Kudos
karthikelango
Enthusiast
Enthusiast

Hi,

In our case reboot the host, remove the host from vCenter, and then re-add the host back fixed the issue.

Reply
0 Kudos