Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

"Unable to connect to the MKS": check the VM console path from the vSphere Client to ESXi

Technical article
VMware

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

When a VM console fails with "Unable to connect to the MKS", the console client could not complete its connection to the ESXi host that runs the VM. Broadcom's knowledge base lists three situations behind it: the client is on another subnet behind a firewall, the name of the ESXi host or vCenter does not resolve to a valid address, or the console is started from vCenter towards the VM. The fastest route to the cause is to name the console type you use, then test the port and the name on each hop.

What the error means

Broadcom's vSphere 8.0 firewall page says the Host Client "uses port 902 to provide a connection for guest operating system MKS activities on virtual machines", and that "users interact with the guest operating systems and applications of the virtual machine" through it. The page adds that VMware "does not support configuring a different port for this function".

Which hops must be open depends on the console type. The TechDocs vSphere 8.0 page "Connecting to the Virtual Machine Console Through a Firewall" (Last Updated November 19, 2026) gives these rules:

  • Browser-based console from the vSphere Client: the vSphere Client must reach vCenter Server on port 443, and vCenter Server must reach the ESXi host on port 902.
  • VMware Remote Console (VMRC) started from the vSphere Client: the vSphere Client reaches vCenter Server on port 443. VMRC must reach vCenter on 443 and the ESXi host on port 902 for VMRC versions before 11.0, and port 443 for VMRC version 11.0 and greater.
  • VMware Host Client (direct to one host): the firewall must allow access to the ESXi host on ports 443 and 902. The same page says: "Do not use the VMware Host Client to connect directly to hosts that are managed by a vCenter Server system. If you make changes to such hosts from the VMware Host Client, instability in your environment results."

Broadcom KB 336884, "Error: Unable to Connect to the MKS while Connecting to Remote Console" (Updated On: 04-20-2026), shows the VMRC variant. The console dialog starts "Unable to connect to the MKS: Could not connect to pipe" and names vmware-authdpipe; the KB's example ends it with "The system cannot find the file specified." The VMRC log line ends "Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period." The VMRC log lines before it show the first failure: "Cannot connect to server SERVERNAME:902: No connection could be made because the target machine actively refused it" and "Failed to connect to server SERVERNAME:902". In the KB's log, VMRC then tries a local socket connection, which also fails, and the console dialog then reports the pipe message.

The KB's own wording of the resolution is shorter: allow the console port 902 to vCenter and to the ESXi hosts. Where the KB and the TechDocs page for your version differ on which hop uses which port, use the TechDocs page as the port map.

Another console message looks similar but has a different cause. Broadcom KB 374599 (Updated On: 05-18-2026) covers "Couldn't establish a connection to the VM web console" in vCenter Server 7.x and 8.x, where the cause is a missing Global.Proxy privilege on the "vSphere Client Service Account" role. That is not an MKS or port fault.

Likely causes

Cause What you see How to confirm
Port 902 blocked between the console client and the host (VMRC before 11.0, Host Client) The VMRC log shows "Failed to connect to server SERVERNAME:902" A TCP test from the client PC to the host on 902 fails
Port 443 blocked from the client to the host (VMRC 11.0 and later, Host Client) The console fails from the client while vCenter itself is reachable A TCP test from the client PC to the host on 443 fails
Port 902 blocked between vCenter and the host (browser console) Browser console fails while the vSphere Client itself works Ask the network team for the rule between the vCenter address and the host address on 902
Port 443 blocked from the client to vCenter Console and the whole vSphere Client misbehave A TCP test from the client PC to vCenter on 443 fails
DNS name of the host or vCenter does not resolve, or resolves to a wrong address The error appears only for some hosts nslookup from the client and from vCenter returns no answer or an unexpected address
Missing Global.Proxy privilege (different message) "Couldn't establish a connection to the VM web console" The role "vSphere Client Service Account" lacks Global > Proxy

Prove the cause before changing anything

These checks only read. They do not change any setting.

1. Name the console type. Is it the browser console from the vSphere Client, VMRC, or the Host Client on one host? The rules above differ for each.

2. Read the exact message. If it names "vmware-authdpipe", the KB shows it for VMRC. The log is in %TEMP%\vmware-USERNAME\vmware-vmrc-####.log on the client PC (the KB's path). Look for the line naming the server and port 902.

3. Test the client hops from the PC where the console runs. Microsoft's Test-NetConnection cmdlet takes -ComputerName and -Port, and -InformationLevel "Detailed" prints the result fields, including TcpTestSucceeded:

Test-NetConnection -ComputerName vcsa01.example.com -Port 443 -InformationLevel "Detailed"
Test-NetConnection -ComputerName esx01.example.com -Port 902 -InformationLevel "Detailed"
Test-NetConnection -ComputerName esx01.example.com -Port 443 -InformationLevel "Detailed"

A good result shows TcpTestSucceeded : True for 443 to vCenter. The two tests to the host matter only for the console types that connect from the client to the host: port 902 for VMRC before 11.0 and the Host Client, and port 443 for VMRC 11.0 and later and the Host Client. A False on a hop the console type needs points at the firewall or the name for that hop.

4. Check forward and reverse DNS. The KB says that when hosts are added by DNS, vCenter and the ESXi hosts both need DNS resolution, and to use the nslookup command from both the client and vCenter to confirm valid forward and reverse entries:

nslookup esx01.example.com
nslookup 192.0.2.21

A good result returns the address the host really uses, and the reverse lookup returns the host name. A bad result is no answer, or an address that belongs to another machine.

5. The vCenter to host hop. For the browser console this hop (port 902) is the one a client PC cannot test. Neither Broadcom's TechDocs page nor its KBs give a command for it. Ask whoever manages the firewall to confirm that vCenter's address may reach the host's address on port 902.

Fix

Change one thing at a time and test the console after each change.

Firewall rule for port 902 or 443

Risk: a firewall change affects every user of that path, and a rule that is too broad opens more than the console needs. Save first: export or print the current rule set with your firewall's own method and keep the file. Back out: remove the rule you added, or re-import the saved rule set, then repeat the Test-NetConnection checks.

Add the missing allow rule for the hop identified above.

DNS record for the host or vCenter

Risk: clients and vCenter cache DNS answers, and other services that use the same name will also change. Save first: note the record's current value from the nslookup output above and from your DNS console. Back out: put the saved value back in the DNS console. Wait for cached answers to expire, or clear the cache on the client and on vCenter.

Correct the A record and the matching PTR record so that the host name resolves to the address the host really uses.

Missing Global.Proxy privilege

For the "Couldn't establish a connection to the VM web console" message only, KB 374599 describes enabling the Global.Proxy privilege on the "vSphere Client Service Account" role in the vSphere Client under Administration, Access Control, Roles.

Risk: changing a role changes permissions for the service account that uses it. Save first: record which privileges the role has now (screenshot the role's privilege list). Back out: untick the privilege you added and save.

Example (illustrative): An administrator in a branch office at 198.51.100.50 uses an older VMRC (before 11.0) to reach a VM on esx01.example.com (192.0.2.21), managed by vcsa01.example.com (192.0.2.10). The error names "vmware-authdpipe". The VMRC log shows "Failed to connect to server esx01.example.com:902". Test-NetConnection to vcsa01.example.com on 443 returns TcpTestSucceeded : True; to esx01.example.com on 902 it returns False. nslookup resolves the name correctly. The network team finds the branch firewall allows 443 to 192.0.2.10 only, adds an allow rule for 902 to 192.0.2.21, and the console starts. Moving the branch to VMRC 11.0 or later would change the need from port 902 to port 443 to the host, according to the TechDocs page, and this branch firewall does not yet allow that either.

Confirm the fix

  1. Repeat the Test-NetConnection tests that failed and read TcpTestSucceeded : True.
  2. Launch the console from the same client, with the same console type, on a powered-on VM.
  3. Launch it for a VM on a second host, to be sure the fix is not specific to one host name.
  4. Check that the VMRC log no longer shows port 902 failures.

What to watch afterwards

  • Keep the three console paths in your firewall documentation, with the ports from the TechDocs page for your vSphere version.
  • After DNS or network changes, test one console per host before users find the fault.
  • When VMRC versions change, recheck which hops need port 902, because the TechDocs page treats versions before 11.0 and 11.0 or later differently.

Risks and limits

  • These commands have not been run or lab-tested.
  • KB 336884 gives its examples for VMRC on Windows. Its resolution lists the console port as 902 to vCenter and to ESXi hosts, which is wider than the TechDocs hop-by-hop rules. Use the TechDocs page for the port map and the KB for the log lines and the DNS check.
  • Neither Broadcom's TechDocs page nor its KBs give a command that tests port 902 from vCenter to a host, so that hop depends on the firewall owner's confirmation.
  • Other vSphere versions can use different ports. Check the firewall page for your version.

Sources