Unable to connect the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period

[gajananfu]

Hi

We are unable to access the VM console  and getting the Unable to connect the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period error on VSphere client. The issue is getting, when we connect through  a VPN network. We tried on multiple systems but same issue.

When we connect through local network, We are able to access.

Please let me know if you have any workaround on the issue.

[Alim786]

Can you please check that you have the correct DNS Server settings on the client that you are using to connect over VPN.

[mars0077]

The VPN solution should be able to provide name resolution. Ping your vCenter and ESX hosts and see if the correct IP comes back. I would create some static host entries in your host file using the FQDN for vCenter and the ESX hosts in question. If this does not solve it, then it may be a firewall issue and the appliance may need to allow all ports required.

[bhards4]

Hi,

Try to vmotion this machine to another host within the cluster. That might resolve your issue.

Regards,

Bhards4

Please mark answer helpful or correct if you find it suitable.

[gajananfu · Accepted solution]

Thanks!!!

VCenter is accessed using IP address, Host and VCenter entries has been created in host file. It seems to be firewall issue.

Could you please let me know which port required.

[gajananfu]

Hi Bhard4,

Thanks !

We are getting the issue on all VMs not a particular VM.

[Alim786]

Ports 80, 443 and 903 required between vSphere Client and vCenter including VM Console.

[gajananfu]

Thanks !!

After allowing all required ports in firewall it's working.

Thanks again.

[Oitsalan]

I had same error and found it only happening to VMs on one host. Turns out the host "Default Gateway for VMkernal" configuration had disappeared.

[frostypaws]

I can confirm this is also the fix. Check your HOST mgmt gateway, for whatever reason the HOST was missing his.

[wirickdg]

I had this very issue this morning when trying to access each of the several VMs I have running on my ESXi 5.5 Hypervisor. I was able to connect to the Hypervisor using the vSphere client. For each VM that I would try to console to I would see the "Unable to connect the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe" error. It turns out in my case that I had a failed drive on the server that had failed a week or two prior to this issue and then that morning I had two drives fail at once. This meant three failed drives on a RAID-6 system. The system basically wasn't working even though it looked like in the Hypervisor that it was. We ended up rebooting the server, and fortunately one of the three drives came back online. This gave me time to get the two failed drives replaced before we suffered another third drive failure. Once the system came back up, the error message went away, and the console worked just fine.

[CERKYR]

Hello,

For the ESXi version 6.5 U2, I have the same problème with VMRC.

In fact, my VCSA have 2 network cards, for 2 different VLAN.

The web interfaces (HTML5 and Flash) are working well.

Only the VMRC is failed with the same error message, through the second network only.

Through the first network, It's working well.

It's like something is not routed.

The VLAN ID is 4095, for the 2 networks.

The ping from the second network to each VM is not allowed; it means that second network can't see directly the VM Inside the first network; it's mandatory to use the vcenter (vcsa) and the VMRC (flash) or Remote Control (html5).

The Remote Control (HTML5) is running, but the keyboard is only with QWERTY, I can't choose AZERTY keyboard.

From WMware, though updates (KB) or other things (configuration), did you have any answer ?

Regards,

[AndreGiesler]

i had the same issue, my solution:

go to Network Adapter, open up ip4 TCP/IPv4.

Expand or Extras i dont know the name of the button in English where sits down in the right corner. but klick it.

got to register DNS clean up all and Append primary and connection-specific DNS suffixes and  Append overarching suffixes of the primary dns suffix, if you dont have this.

open up command prompt and enter: ipconfig /renew

that was the solution for me, to get it work again