UNABLE TO CONNECT TO THE MKS : COULD NOT CONNECT TO PIPE

[dquintero]

Hi All im getting the following error while trying to open a virtual machine console through thev vcenter client.

UNABLE TO CONNECT TO THE MKS : COULD NOT CONNECT TO PIPE
.\PIPE\VMWARE-AUTHDPIPE: UNKNOW ERROR 2 (0X2)

While trying to the same on the Web Access i get the same error and also the following one

ERROR OPENING THE REMOTE VIRTUAL MACHINE <IP>\16: CANNOT COMPLETE LOGIN DUE TO AN INCORRECT USER NAME OR PASSWORD

At first i thought it was perhaps some kind of name resolution error but when i got the second message it made me think that

perhaps is more of a security issue

any clues in why im getting this error ?

Att,

Daniel Quintero

[aleksey]

are you using a non-admin (non-root) user to connect remote console to a VM? Which user was used to create this VM?

[dquintero]

the vmachine was created by root and im trying to use root to access it .

Att,

Daniel Quintero

[aleksey]

Can you please run "vm-support" or gather diagnostic bundle from the VI client and PM it to me?

thanks.

[dquintero]

Here is the support data.

Is a brand new installation and im having the same behavior in 3 servers.

Att,

Daniel Quintero

[dquintero]

Hello

After some investigation i traced back the problem to some network issues related to NAT

to me it seemed extrange since the console was the only thing that was miss behaving

but then again the virtual machine console has always been extremely sensitive to

network issues.

Thanks for the help,

Daniel Quintero

[aleksey]

Good to know. I poked around the logs and did not see anything interesting jumping out so I was scratching my head on what was wrong. Glad to hear that you got it working.

-aleksey

[theDern]

I have the same issue currently, what was the NAT problem?

[dquintero]

Hi,

it seemed the console wouldnt work unless i was in the same lan segment of the vmware server

and had the correct name entrys in the server / dns .

I was never sure if my gateway was the problem or if i had a bad network configuration but after i

set my admin ip in the same range everything started working alright

hope it helps

Att,

Daniel Quintero

[theDern]

Thanks.

my ip's are 192.168.1.4 and 192.168.1.8 respectively, still have the pipe error.

[AnalogKid99]

Hi

Did you ever resolve this issue.

For me - I have exactly the same issue.

I dont believe it's the ESX server - as 2 out of 3 of my physical Windows XP laptops, running Vsphere client can access the VM Consoles, the other always goes black, highlights the MKS, PIpe and vmware-authd issue.

Regards

[ssg33w]

I am having this problem too. I am using ESXi 4.0 Server, with Windows 2008 32 bit platform. All attempts to use vmware-vmrc.exe to load a console directly has consistently come back with the MKS authd error. I am required to use the -u and -p options. This is a standalone envirornment without Internet access. I downloaded the most recent VSphere Client which did not resolve the problem. I am unable to use web based access due to GPO policy constraints and not permitted to change the GPO.

Thanks for the help