What is this?

This is basically where I write down stuff that I work with at my job as a GIS Technical Analyst (previously system administrator). I do it because it's practical for documentation purposes (although, I remove stuff that might be a security breach) and I hope it can be of use to someone out there. I frequently search the net for help myself, and this is my way of contributing.

Wednesday, November 24, 2010

"Unable to connect to the MKS" error when using vSphere Client

Had this strange little incident today where three new vmware esxi 4.1 hosts suddenly would not let me see the console for any of the virtual machines from my vSphere client.

I would always get the following error:

"Unable to connect to the MKS: Failed to connect to server myesx.domain.intern:902."

Turns out that the DNS-records in Active Directory were messed up so instead of pointing to the management network interface of my esxi-servers, they were pointing to some dhcp-addresses. It could have happened after fiddling around a bit when setting up a new management network. I presume esxi isn't able to renew ddns registrations (I am after all using static addresses on the management network interface). Anyway a simple static registration of the servers in DNS took care of the problem instantly.
Posted by at
Labels:

1 comment:

  1. Anonymous31/1/13 3:47 PM

    I had this same problem a few times.. it turns out that I had forgotten to configure NTP on the ESX hosts, so when the VMs started up, they had the wrong time by over 8 hours. I think this is what caused the records to be invalid.

    ReplyDelete

Subscribe to: Post Comments (Atom)