Unable to connect to MKS. Failed to connect to server {name.xyz.com}:902

[spindle77]

Cannot seem to Launch Console from within vSphere web-client (v5.5.0.13012).

It has worked intermittently, but now it seems to not work at all...

Keep getting the error "Unable to connect to MKS. Failed to connect to server {name.xyz.com}:902"

Using the VMware-ClientIntegrationPlugin-5.5.0

Tried different versions of browsers, most recently, FireFox v31 & v36, Chrome v38

Tried rebooting ESX server (W2K8R2) where vCenter (v5.5.0.40799) VM running.

Tried rebooting host (W2K8R2) where web client is running.

All attempts are meeting with the same resulting error.

Any ides?

[Alistar]

Hello,

this is a firewall problem - make sure that from the client you want to access the remote console from, the destination port 902 is open on the ESXi host itself (the traffic goes via management network), so you would make a rule:

ALLOW clientpc:all -> esxihost01:902 (all your ports from your PC can initiate a connection to destination port 902 on the ESXi host that provides you with console video)

[spindle77]

Thanks for the tip on the firewall, but that can't be the issue as it works intermittenly. In fact, after posting the discussion, was able to un-install plugin, and re-install, on my vCenter VM, and then open web client with Chrome and successfully launch console.

Previously I had done the same from a remote Windows 2008R2 host using web client and FireFox.

Seems to be after some amount of time working, it just stops working and haven't found the correct process to fix.

Thought it was to reboot to the ESXi server where the VM running the web client to VC was running, but that didn't fix the issue yesterday.

[vfk]

Hi, I suspect you have dns resolution issue, you need to able to ping esxi host by short name and fqdn.  When you experience this issue again, try ping esxi host and vm by short name and see if they are fully responding.  It could be dhcp lease dynamically updating dns or something like that.