VMware: VM Console error: Unable to connect to the MKS: Failed to connect to the server (1010828)

“Unable to connect to the MKS: Failed to connect to the server 172.16.254.202:902” or “Unable to connect to the MKS: Failed to connect to the server no such host is known”

image

Solution:

To avoid losing access to the ESX host, perform the following steps:

1. Add the ESX server in your DNS

2. Edit your hostfile on the workstation (C:\Windows\System32\Drivers\etc\hosts\) and add your ESX server

 

After adding the ESX by DNS in my hostfile and restarted the VI Client I was able to open Console screen.

[ad#ad-banner]

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has 15+ years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

33 thoughts on “VMware: VM Console error: Unable to connect to the MKS: Failed to connect to the server (1010828)

  1. VMPros:

    Could you please provide a more detailed work through of this? I’m having issues with this and the above instructions don’t seem to be getting me to far.

    Cheers

  2. Jay Transporter, Me: you need to add the FQDN in your hostfile how the ESX host is added in your vCenter. So if you added ESX01.VMpros.local to your VC you need to add ESX01.VMpros.local in your hosftfile, if you added only ESX01 as name in your VC you need to add ESX01

  3. Hi,

    Would this fix also work for remote connections?
    I am connecting to an external IP which is then being port forwarded to the internal IP of the ESX server. I have added the hostname of the server to my local PC hosts file and it resolves to the external IP.

    But i still get the error above.

  4. I had this problem as well, could not communicate to ESX server. i had the right GateWay address in my V Sphere server but not on my ESX host.

    From client select your hosts –> configuration –> DNS & Routing (under software)—> Routing tab

  5. In my case everything was functional and the only problem was the black screen. Somehow the ESX host have lost the default gateway. After correctly config its works.

  6. Can’t beleive this was the issue! 🙂 WORKS perfectly once entered in my local host file and once the ESX client is restarted for some reason before I did this only 1 of my three hosts was gicing me access to a console in the cluster after entered in the host file all console worked remotely thanks thanks thanks.

  7. Hey i have the same trouble but, i have already add to de domain and to de etd/hosts i think de problems is that mi vcenter is in the subnet 10.1.1.x the same form the host but the vcliente is in the 192.168.1.x there is a way to this ???? sorry about mi poor english thanks a lot men

  8. Dear Jack

    Thanx. A small entry in Default gateway was missing. Now problem resolved…. Once again thanx…
    From client select your hosts –> configuration –> DNS & Routing (under software)—> Routing tab

  9. Have added the FQDN of the vCentre server name to the host file but does not work. However, we have 2 VC servers and I am able to connect to the console on one but not others. My colleagues do not have this issue even though client OS and VI client are the same.
    Any ideas??

  10. This is a pretty generic error, for whatever reason the client software cannot connect to the KMS (Keyboard, Mouse, and Screen).

    In NEARLY every case this is a communication issue, either the machine running the client software cannot resolve the name of the ESX host that is hosting the virtual machines, or TCP Port 902 is being blocked by a firewall.

    1. If you can’t simply pop the correct name in your DNS, then add the name and IP to the machines, (the one running the VI client software) host file. You will locate this in;

    C:\Windows\System32\Drivers\etc

    2. Open it with Notepad, and add the IP and name of your ESX host(s), Note: I’m also putting the name and IP of my Virtual Center server as well. Save the file and try again.

    Example:

    10.1.16.25 css-vc01.css.local
    10.1.16.21 vmh-css4.css.local
    10.1.16.23 vmh-css5.css.local

    3. You should now be able to connect.

    It’s NOT DNS!

    If you can happily resolve the name and are sure that the port is not being blocked, then have you made any IP changes? Is the default gateway on the ESX Server set correctly? And finally restart the management agents on the host, either from the console, or by running ‘/sbin/services.sh restart’.

  11. Pingback: Keep Reading
  12. Pingback: travelodge

Leave a Reply

Your email address will not be published. Required fields are marked *