Error connecting to authd on host

gimosuby
gimosuby used Ask the Experts™
on
We have Virtual Center 2.5 installed on a server. When trying to connect to the console for a virtual machine through the VMWare Infrastructure Client (From the Vcenter server), we get the error: Error connecting to authd on host. We get the same error when going through a webbrowser to the Virtual Center server, or directly to the ESX hosts. However it works just fine if we connect from another workstation to the Virtual Center server.  

I've researched and tried about everything to fix this but without luck. The VCenter server and the workstation on which it works fine are running the same version of VIC.

Your help would be very much appreciated.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2010

Commented:
Since you didn't provide what you tried, I'll post these links to see if they help:
http://communities.vmware.com/message/733306;jsessionid=1488313EC3F438936D6480CFE4336999
http://www.experts-exchange.com/Software/VMWare/Q_24914351.html
http://communities.vmware.com/message/1325096;jsessionid=562198590FD473BEF79394C24299DE74

Another thing I would try, if you're able, is to reboot your Virt Ctr server.

Also...just so I'm reading your post correct: are you saying that if you use the client on your workstation, it's fine, but if you use the client on the virt ctr server, you get that error?

Regards,
~coolsport00

Author

Commented:
Yes, you're reading that correct. It doesn't work using the client on the virt ctr server, whether I connect to localhost, or remote ESX servers through client or webbrowser. When I try it from my own workstation it works fine whether I connect to the virt ctr server or straight to the ESX server. the VCI clients are the same version on the virt ctr server and my workstation.

What I've tried.
- Uninstall and re-install virt ctr server and VCI.
- Rebooting

There is no firewall between the virt ctr server and my ESX server, everything was working fine until recently. I can't think of any big changes that occurred that could have caused this...
Top Expert 2010

Commented:
A couple other things to try...have you (or are you able to) rebooted your ESX servers? Also, what if you typed in the IP or hostname of your VC server instead of using "localhost"?

~coolsport00
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Thanks for your suggestions. I've tried connecting to the IP and hostname of the vcenter server using the VIC on the vcenter server but no luck. I've also tried to connect straight to the ESX servers which didn't work either.
Rebooting the ESX server didn't make a difference and since I'm able to connect just fine to it from another workstation I don't think it has anything to do with my ESX servers.
Top Expert 2010

Commented:
Hmm...since access to 'authd' requires port 902 to be open, the only other thing I can suggest is to see if the Windows Firewall is enabled and, if it is (and you require it to be) to add port 902 as an exception.

Regards,
~coolsport00

Author

Commented:
Windows Firewall is not enabled so that can't be the problem...
Top Expert 2010

Commented:
I've run out of searches and possilbe solutions :) This may be something you'll need to contact VMware Support for. Sorry I couldn't get this resolved for you :(

~coolsport00

Author

Commented:
Okay, I'll post an update once I've got it fixed. I knew this was going to be a hard one as I did all my homework before posting this question. Thanks for your efforts.
Top Expert 2010
Commented:
Yes...be curious to know the answer myself :)
Commented:
Okay, here we go...

I removed VMware Virtual Center and Virtual Infrastructure Client (VMware vCenter Server 2.5 Update 6) from the server, then downloaded the VIC from the ESX server (VMware ESX 3.5 Update 4) with my webbrowser. I installed that VIC and it worked fine, then I uninstalled it and downloaded and installed the VIC from VMware vCenter Server 2.5 Update 5 and that worked fine, so then I installed VMware vCenter Server 2.5 Update 6 and I got the error again. So now I'm running VMware vCenter Server 2.5 Update 6 with the VIC of VMware vCenter Server 2.5 Update 5 and it works. From the workstation I'm still able to connect just fine using the VIC from VMware vCenter Server 2.5 Update 6.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial