Comments on: Unable to connect to the MKS: Failed to connect to server XXXXXX:902

By: Elvys

Elvys — Mon, 14 Nov 2011 18:16:21 +0000

I have the following error “Unable to connect to the KMS: Internal error” but it is not form ESX Server. All the setting in ESX Servers described above are already set. This error happen from Remote Console in vCloud Director.

Any thoughts.

By: Darto

Darto — Mon, 24 Oct 2011 03:13:15 +0000

Work like charm !!

1. firts try add hosts dns, then ping the host if reply then ..
2. seconds add vmauthd.server.alwaysProxy = “TRUE”

thanks for info

By: Ed Ward

Ed Ward — Mon, 31 Jan 2011 19:05:02 +0000

I’m having this same issue with ESXi 4.1. “vmauthd.server.alwaysProxy=TRUE” is already in there by default.

By: Dion

Dion — Thu, 13 May 2010 23:02:29 +0000

Seems Windows 7 was blocking my connection to one of the hosts and only on port 902… I just rebooted windows

By: Network

Network — Tue, 30 Mar 2010 15:43:47 +0000

We had the same problem, it was an network error (the port 902 was closed by a firewall). The best thing to discard being that is telneting to that port:

telnet IPADDRESS 902

You should receive something like:
“220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported”

By: Cool2Be

Cool2Be — Fri, 12 Mar 2010 01:14:50 +0000

I ran into the same problem and it was the same issue.

To fix it, add the following line to the /etc/vmware/config file in the VMware ESX Service Console:

vmauthd.server.alwaysProxy = “TRUE”

By: sham

sham — Wed, 06 Jan 2010 21:49:59 +0000

I run vsphere client remotely… and on the other end this particular fix has already been employed.. yet i have this issue?