VMware vSphere

 View Only

 VMWare Remote Console Connection Error (but web console works)

Steven Duzevich's profile image
Steven Duzevich posted Aug 20, 2024 05:56 AM

Issue: I launch the remote console from vSphere.  Application opens and I can boot the virtual machine with the play button.  Black screen remains for 10-20 seconds then a popup saying "connection error" comes up.  I can press OK and then continue to use the power control buttons but the screen remains black and there is no input.  In the meantime, the web console is totally fine, display and IO works.  Can't seem to add a disc image from the remote console, so it's not just an issue isolated to the display anyway.  By the way, tested on virtual machines with and without OS's.

Log: quite unenlightening.  Compared it to my coworkers successful log and it matches all the way through until:

MVNCClient: received socket error 6: Connection error 
mks MVNCClient: Setting vncClient.mksConnectionError, previous error is 0, new error is 1 

Which is then ollowed by a series of "disconnecting" logs. 

vSphere Client version 7.0.3.01100
VMWare Remote Console version 12.0.3 build-21263813 
vSphere hosted on our server vcenter.ourdomain.de 

  • ping vcenter... works
  • nmap -p 443,902 vcenter...

    • 443/tcp open   https

    • 902/tcp closed iss-realsecure 

Windows Firewall has been disabled, enabled, application allowed, TCP and UPD all ports allowed on domain, public and private.  I have ESET endpoint security installed, but it's firewall is permanently disabled.

The VM must be fine, as it is accessible from other (all also Windows 11) computers on our network. 

One article (VMware Remote Console 11.x - connection error (broadcom.com)) suggested (quite illogically) to use the legacy connection options:

pref.preferWebMKS = "FALSE" 
pref.preferWebRemoteDevice = "FALSE" 

This results in an error - the application hangs for a while then edv-108.ourdomain.de couldn't coldn't connect on port 902 (I'm not sure where edv-108 comes from - this is not the vcenter IP nor is it the virtual machine I was trying to launch).  Obviously, because VMRC v12 and vSphere v7 match to needing port 443.  Found another guide that said to put those settings back to true to "fix connection error."  So that takes me back to my original connection error problem.

I can't think of anything else I can do, but I'm new to this kind of stuff (my background is all programming not network or virtual machine stuff).  Anyone have any ideas?

Steven Duzevich's profile image
Steven Duzevich

Ups, server had an unexpected **** on it.  Solved...