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

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” or “Unable to connect to the MKS: Failed to connect to the server no such host is known”



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.



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

More Posts - Website

Follow Me:

Categories: VMware Tags: , , , ,
  1. Ayuba
    October 1st, 2009  (Quote) at 07:34  (Quote) | #1


    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.


  2. December 18th, 2009  (Quote) at 10:15  (Quote) | #2

    Hello Ayuba,

    Updated my post, hope you can reconnect your Console with this solution!

  3. December 30th, 2009  (Quote) at 21:51  (Quote) | #3

    Great, stupid solution but it works 🙂 thanks… !!

  4. January 26th, 2010  (Quote) at 16:50  (Quote) | #4

    Hey dude! This is not working for me. I added to the hosts file the container server and also one virtual machine (for which I tried to open the console) but nothing…

  5. me
    April 22nd, 2010  (Quote) at 07:16  (Quote) | #5

    Same to me… i added to entry in the host file, but it doesn’t work

  6. July 9th, 2010  (Quote) at 11:37  (Quote) | #6

    Thank you soooo much for this solution, simple one

  7. August 29th, 2010  (Quote) at 13:15  (Quote) | #7

    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

  8. September 21st, 2010  (Quote) at 22:03  (Quote) | #8
  9. Luis Vidal
    February 10th, 2011  (Quote) at 06:46  (Quote) | #9

    Great tip, my friend. It solved my issues with this. Thanks.

  10. thkdiff
    March 28th, 2011  (Quote) at 09:07  (Quote) | #10

    I think it’s caused by dns resolvation doesn’t work

  11. Bilbo
    April 15th, 2011  (Quote) at 12:08  (Quote) | #11


    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.

  12. April 28th, 2011  (Quote) at 18:49  (Quote) | #12

    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

  13. Ashish Patel
    May 2nd, 2011  (Quote) at 16:42  (Quote) | #13

    make sure you can connect the esx server. ping it.. if you have to add any static route to reach it.. make sure your pc resolve esx server’s fqdn.

  14. Thomas
    May 9th, 2011  (Quote) at 10:55  (Quote) | #14

    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.

  15. Ray
    June 25th, 2011  (Quote) at 04:11  (Quote) | #15

    That worked for me. My ESX somehow lost the default gateway. I re-added it and it is now happy. Thanks


  16. steve
    September 14th, 2011  (Quote) at 01:55  (Quote) | #16


    How can you add an entry to the host file of a VM you can’t power up because you get the “Unable to connect to the MKS” message? : )

  17. October 21st, 2011  (Quote) at 07:15  (Quote) | #17

    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.

  18. Bhuwan
    October 25th, 2011  (Quote) at 09:11  (Quote) | #18

    Try with rebooting host once .. In my case this resolved the issue .. Host lost it’s connectivity with Storage ..

  19. FChrist
    October 28th, 2011  (Quote) at 14:28  (Quote) | #19


    Good solution

  20. November 1st, 2011  (Quote) at 09:41  (Quote) | #20

    Just to share, i tried flushing the DNS in CMD with command below, and rerun the VI client. Worked like a charm!
    ipconfig /flushdns

  21. Dieter
    November 18th, 2011  (Quote) at 01:02  (Quote) | #21

    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

  22. Shakeel
    December 29th, 2011  (Quote) at 23:40  (Quote) | #22

    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

  23. thangtd1
    February 20th, 2012  (Quote) at 04:29  (Quote) | #23

    From client select Configuration -> Advanced Settings -> Config -> Default -> security -> host
    hii ok.

  24. Semih
    February 27th, 2012  (Quote) at 16:43  (Quote) | #24

    My VRMC opens in my windows7 laptop.

    But i cant use on Windows 8 DP

  25. MG
    March 28th, 2012  (Quote) at 15:38  (Quote) | #25

    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??

  26. Pablo
    August 10th, 2012  (Quote) at 02:25  (Quote) | #26

    Este problema es de firewall

  27. Pedro
    October 4th, 2012  (Quote) at 21:55  (Quote) | #27

    Nice its Work!!!

  28. david
    December 21st, 2014  (Quote) at 14:09  (Quote) | #28

    thanks man .
    this was very helpfull

  29. Niko
    January 9th, 2015  (Quote) at 02:07  (Quote) | #29

    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;


    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: css-vc01.css.local vmh-css4.css.local 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/ restart’.

  1. at | #1
  2. at | #2
  3. at | #3
  4. at | #4