Prabin Lama
asked on
VMware Console Access Error
I encountered a strange issue:
When trying to access console of any VM, the console throws error: "Unable to connect to the MKS: Could not connect to the pipe \\.\pipe\vmware-authdpipe within retry period."
I told the client to add ports 80, 443 and 903 in their firewall, but he says all the ports are open on the firewall to the management network (192.168.A.0). He checked the gateway of ESXi DCUI and saw vMotion network (192.168.B.0) gateway and he changed it to management network (192.168.A.0) gateway. Then what do you know, the VM console opens. Now, I understand the vMotion gateway was put there when configuring vMotion automatically but it doesn't make sense from a networking perspective.
Any ideas on why this is happening? This is on ESXi and vCenter 6.0.
When trying to access console of any VM, the console throws error: "Unable to connect to the MKS: Could not connect to the pipe \\.\pipe\vmware-authdpipe within retry period."
I told the client to add ports 80, 443 and 903 in their firewall, but he says all the ports are open on the firewall to the management network (192.168.A.0). He checked the gateway of ESXi DCUI and saw vMotion network (192.168.B.0) gateway and he changed it to management network (192.168.A.0) gateway. Then what do you know, the VM console opens. Now, I understand the vMotion gateway was put there when configuring vMotion automatically but it doesn't make sense from a networking perspective.
Any ideas on why this is happening? This is on ESXi and vCenter 6.0.
Please use DNS and FQDN to access your Hosts and VMs.
Please use FQDN to access your Hosts and VMs.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Author solved issue
https://techhead.co/unable-to-connect-to-the-mks-vmware-vsphere-console-fix/