After adding hosts to vCenter, when I try to upen the VMRC, I get the error: Unable to connect to the MKS: Internal Error
First off, it is not the usual DNS resolution of Host IP addresses MKS Error! This is something entirely different.
One unusual thing in the manifestation of this problem is that by powering off (fully off, not a restart) and then powering on the VM in question, the console will work for that VM, but the console will continue to malfunction for other VMs on the same host until those VMs are vMotioned or completely power-cycled!
Here is the workflow:
- I stand-up a new ESXi (patched and firmwared to latest updates)
- I build a Windows or Linux VM to serve DNS and/or be an AD Domain Controller
- I install the VCSA (or Windows vCenter)
- I log in and test forward and reverse resolution for all hosts on the Broadcast Domain
- I add the ESXi Host (and any other hosts) to vCenter
- I try to open a VMRC and get the MKS error!
This is a minor issue except for the VCSA itself!
Any ideas?