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

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?

By: mike

mike — Sun, 27 Dec 2009 14:26:52 +0000

I am running ESX4i on a remote machine and using vsphere client to log in. Where do i change this when i log in from the client side with vsphere? I can’t seem to find it in the configuration.

Thanks in advance.

By: Greg

Greg — Tue, 01 Dec 2009 12:35:57 +0000

And where did you find the information?
Thanks

By: Greg

Greg — Tue, 01 Dec 2009 12:33:54 +0000

So this worked after several other fixes did not (or were already accounted for). However, I don’t really accept the fix without an explanation. What is /etc/vmware/config and how, where & when is it used?
Please.

Thank you