VMRC switched its default transfer protocol to WebSocket in recent releases, which results in the port of daemon service in the host changed as well:
VMRC Version | <11.0 | 11.0 | >11.0 |
Default protocol & port for Mouse/Keyboard/Screen connection | TCP 902 | WebSocket 443 | WebSocket 443 |
Default protocol & port for "remote device" connection | TCP 902 | TCP 902 | WebSocket 443 |
A process that is responsible for rendering the guest video and handling guest operating system user input.
And considering the support of WebSocket in vSphere releases are different:
vSphere Version | <7.0 | >=7.0 |
Support WebSocket based Mouse/Keyboard/Screen connection | Yes | Yes |
Support WebSocket based"remote device" connection | No | Yes |
The combined matrix is:
<VMRC 11.0 | VMRC 11.0 | >VMRC 11.0 | ||||
MKS | Remote Device | MKS | Remote Device | MKS | Remote Device | |
>= vSphere 7.0 | 902 | 902 | 443 | 902 | 443 | 443 |
< vSphere 7.0 | 902 | 902 | 443 | 902 | 443 | 902 |
For those combinations fall into the 443 (port) category, by default, VMware Remote Console requires direct access to port 443 on ESXi hosts. If VMware Remote Console cannot reach port 443 on a host, for example due to firewall rules, VMware Remote Console will be unable to access or pass through a remote device to virtual machines on that host.