Anyone has this problem? I loaded vSphere 4.0 from ESX 3.5 host and all seems working fine yesterday, after resume more testings and this error popped up:
"Unable to connect to the MKS: Cannot connect to host failed on vSphere 4.0 and client
After google searched, I was able to resolved it by placing DNS entries on the client machine c:\windows\system32\drivers\etc\hosts file point to my ESX host name, FQDN, and short name and it worked fine. I'm curious why this happened though?
What's MKS means in this case? Microsoft Key Server or Management Key Server????????????????
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
VMware vExpert 2009
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant