Problem: From the Virtual Infrastructure Client, I log in and can do whatever I want except see a VM’s console. The VM can power up, I can modify the VMs, but when I go to the console, it just gives me a black blank screen. When I use open console, I get a timeout. I set up the vmx file so that I could use vnc to connect to the console and it works fine. When using the webAccess, I can see the console just fine too. What gives?
In the VI3 server, connections are handled a little differently. Incoming RC connection go to port 902 in the COS: vmware-authd service Then, the MKS (mouse, keyboard, screen) connection happens on port 903 – vmware-vmkauthd listens on port 903. Since connections to port 903 are forwarded to COSShadow, COS would not see those packets. The client actually makes a request on port 902, but then, the server gives a redirect to the client to connect on port 903. If there’s any type of NAT in between or some other network tweak, it could cause this to fail.
Here’s the workaround:
1) Open up the /etc/vmware/config file and append to the bottom:
vmauthd.server.alwaysProxy = “TRUE”
2) Restart the management agents by running:
/etc/init.d/mgmt-vmware restart
3) Disconnect and reconnect the Virtual Infrastructure Client or VirtualCenter from the ESX server.
This will avoid the authd redirection and it should allow your remote console to function properly.