How to solve the unable to connect to the MKS:Internal error problem in vc

Today, I will talk to you about how to solve the unable to connect to the MKS:Internal error problem in vc. Many people may not know much about it. In order to make you understand better, the editor has summarized the following for you. I hope you can get something according to this article.

VC (vCenter Server) 5.5in the production environment, starting a virtual machine console displays the following error: unable to connect to the MKS:Internal error. Unable to connect to MKS: internal error. MKS here is really not clear what it refers to, search can not find a reasonable explanation, it is estimated that the link problem.

As shown in the figure

Consult a technician at VMWARE and be told to try the following solutions:

Service mgmt-vmware restart

/ etc/ vmware/config add vmauthd.server.alwaysProxy = "TRUE"

Check whether port 902 of client is occupied

After both scenarios 1 and 2 failed, I reinstalled VC (vCenter Server) and VMware vSphere Client 5.5 on a PC, then connected the former with the latter and added an ESX5.5 host in the environment to the management side, and everything was fine after starting the virtual console.

Or migrate the failed virtual machine to another physical host in the cluster and return to normal.

Conclusion: it may be the problem shown in point 3, but after I rebooted the VC in the environment, it worked miraculously. It is hard to understand. It is recommended that friends who encounter this problem can try to restart the VC host or migrate the virtual machine first. If it does not work, please try the above solution again. Of course, no more, it's okay to try it again.

After reading the above, do you have any further understanding of how to solve the unable to connect to the MKS:Internal error problem in vc? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.