The console has been disconnected. Close this window and re-launch the console to reconnect.

[yobah]

Good Morning All,

I am having an issue when trying to connect to any VMRC console via the vsphere 5.5 webportal that is running on a cluster. I was wondering if someone could please point me in the right direction?

My environment currently looks like this:

1) vSphere 5.5

2) 10 Datacentres, with 7 being standalone hosts (all VMRC consoles work on these hosts), and 2 with Clusters (VMRC doesnt work)

NTP, DNS etc all work fine.

Whenever I try to connect to the console, I get the following error:

The console has been disconnected. Close this window and re-launch the console to reconnect.

The only difference I can see between the standalone hosts and cluster hosts are that they have been added to vcenter using the FQDN, as the clusters are using their IP addresses.

Thanks

Paul

[CrashTheGooner]

Dear Yobah,

Kindly restart the VM and it should be working fine.
However depending up on the priority of VM restart depending up on the downtime.

[yobah]

Hi Crash the Gooner,

Thanks for the quick reply.

I have tried shutting down/rebooting/vmotioning the VM to no avail. I am still getting the same error

Thanks

Paul

[yobah]

Has any one else seen this issue before? I have now tried the following to no avail:

1) Rebooted the VM

2) Shutdown the VM

3) Rebuilt new VMs.

I feel this is a cluster issue, or the way in which the host has been added to vcentre (using the IP address, rather than hostname).

[yobah]

Turns out that isn't the issue either. I have rebuilt the cluster and am still getting the console disconnect.

[Rohitekumarshar]

We logged case with VMware for this. It turned out to be SSL issue. We were told to remove the host from the cluster and add it again to refresh the SSL certs. It works after that. We were able to open the console of VM.   VMware PR for this is -2094147

[Murali_Patil]

Try this VMware Knowledge Base , also remove the vm from inventory and re-register the vm should slow the issue.

[dharmenderkalra]

Simple disconnect & reconnect the host also fix the issue for the underlying VMs part of that host