VMware Cloud Community
csrnet
Contributor
Contributor

MKS: could not connet to pipe \\.\pipe\vmware-authdpipe

Hello Formum members,

I am having a little problems with ESXi 5.1 and had the problem appear with the previous 4.1.

Details as follows:

We had ESXi 4.1 installed on a Dell 1950 (2xdual core 3GHz 16GB RAM) and wanting to test vCenter Server, did the install on another system. Everything worked until we removed everything from vCenter at which point we started getting "MKS: could not connet to pipe \\.\pipe\vmware-authdpipe: The system could not find the specified file". Naturally as per the VMware KB, we removed all of the VMs and VMs Host from vCenter. We then turned of the separate vCenter server host and tried rebooting each VMs and then VMs Host, no luck here either. In an effort to put this error to bed, we did an upgrade of ESXi 4.1 to ESXi 5.1u1, this did not solve the problem. Anything to do with vCenter was removed from the XP machine, as fas as I can find. Looking through all of the logs has not brought us any further.

There is no firewall or NAT between the VMs Host and the vSphere client computer running XP;

Firewall on XP is disabled

Everything is on the same subnet;

Everything has static IP addresses;

2 DNS servers active, correct and serving names - forward and reverse;

No active directory configured or running;

All the VMs were setup through the vSphere client logged in as root and has always been the case - even when it was working previously;

This affects all the VMs we try to access (3xFedora 18, 1xRedhat 6, 2xOpenBSD 4.9);

VMware Tools is only installed on the Fedora and Redhat VMs.

/etc/vmware/config has: vmauthd.server.alwaysProxy = "TRUE"

Many thanks in advance,

chrisb

0 Kudos
0 Replies