Console connect error message

[Goodin]

We are at version 5.5 of ESXi.  Whenever we try to attach to the console from vCenter, we get this error:  Unable to connect to the MKS:  Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.

What gives?

[admin]

Hello,

This should help you

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203201...

Thanks,
Avinash

[Goodin]

Already tried that and I had no variables called User.

Josh

[admin]

check this link hope it will help you.. http://adriank.org/vmware-vsphere-5-0-vm-console-shows-unable-to-connect-to-the-mks-console-access-t...

[a_p_]

When you say "... we ...", does that mean you see the same issue for multiple users on different PCs? In this case you may want to check whether any Antivirus/Internet Security/Endpoint Protection or Firewall application causes this issue.

If it's a single PC run ipconfig /flushdns (with the vSphere Client closed) to see whether this helps. Btw. are you able to access the VM's console using the vSphere Web Client?

André

[Goodin]

"We" all use a single terminal server to manage vmware.  Vcenter client is installed on this server.  Everyone is getting the error.  Windows firewall is diabled via GPO, we uninstalled Endpoint protection just to see if it was causing isusues.  No resolve for either.  Also ran ipconfig /flushdns.  nothing.  We are able to access to the them through the web client, but my boss wants the desktop client working. 

[rand0med]

We had this same issue in one of our clusters running VMware 5.5.

On the one system that wasn't working, we found it had a different version of Java than the other systems. Once we updated the Java client and cleared out the old ones, the system was able to view the console via vCenter.

[ressdvmware]

We are having the same issue.  Just started last week.  Was a fix action ever found for this error?  The last update done to our workstations was on 1/5/2015 and that was MS14-080 (KB3008923) which had some IE 10, IE11 and ActiveX updates.

[vAnswers]

Is this issue with all VM's? or a particular VM?

Reinstall vsphere client again and try once. Hope you have checked DNS resolution for both ESXi and vCenter should be working fine from your client OS.

[ressdvmware]

I was hoping to avoid that, but will give it a try...  this issue is with opening the console for all VM's.  DNS is working fine.

[ressdvmware]

Reinstalling the client did not correct the issue...

[heavyvm]

is The ESX-Host on HP Hardware? Then trey this link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=208561...

I have the same Problem since a week.

[ItsButters]

I just had this happen to me connecting to ESXi 5.5 from a notebook on the network. If you have a wi-fi connection on the terminal and a wired connection connecting to different networks this may be the cause. I turned off my wi-fi and attempted again and it worked just fine.

[DJMarzetti]

Same here.  As soon as I switched to a wired connection, it was fine. 

[TurdFerg]

I just experienced this same issue with a Greenfield installation. My issue was resolved by pointing my local computer to the same DNS server as the VCSA in my network settings, and adding the FQDN of the VCSA in the "C:\Windows\System32\drivers\etc\hosts" file. My local system resides on a different subnet,connected via WI-FI, and the combination of the two settings resolved the issue. The oddest thing about this is that I could connect directly to the host with the client and launch a console to the VMs on that host with no problem. Hope this help.

[Shambiesails]

I ONLY get this error when trying to connect directly to the vCenter Server.  When connecting to ESXi hosts, it works fine. Using 5.5 update 2 for both ESXi and vSphere client.

[CoolRam]

Go and check the Size of the vmdk file . If the file size is 0 then you have lost connectivity with your VM. if this is not the problem then please do connect your VIClient again it will work.

[TobiasArvastsso]

Its like TurdFerg mentioned. When you get this error when connecting to vcenter server and use console its almost always a DNS problem of some kind. one other solution can be just to flush your DNS on the client or server you try connecting from. Even if you get right name resolution when using ping or connect to the vcenter server there can be a problem in the cached DNS file on the computer/server that are preventing you from get the display from the vcenter server. Need to keep in mind that the hosts will route the display from the console through vcenter and thats why it works when connecting directly to the host. vCenter loves DNS and in older version of vcenter and esx it would create more problems.

[ddeevvaanngg]

worked. created entry in host file on local client for esxi servers

entries added to host file on local workstaion. replace hostname and ip with yours

192.168.1.100  esx1

192.168.1.101 esx2