Hello,
I got a virtualCenter Server 2.5.0 with the Client 2.5.0.
Within the virtualcenter I got an esx server 3.0.2. Something got messed up. When I try to open a console of a VM on the ESX, I get the message:
"Cannot connect to host <IP>: A connection attempt failed because the connected party did not properly respond after a period of time, or estalished connection... "
I know, that for the console the esx needs to be accessed on port 903. I see it in tcpdumps and in the log on the esx:
snip
vmware-authd[4334]: Found vmkauthd: /usr/lib/vmware/bin/vmware-vmkauthd-start
vmware-authd[4334]: Redirected mks to 192.168.12.6:903
xinetd[1317]: START: vmware-authd pid=4606 from=192.168.12.25
vmware-authd[4606]: login from 192.168.12.25 as 52a024e3-7569-9188-6c91-e4711ee8c409
vmware-authd[4606]: Found vmkauthd: /usr/lib/vmware/bin/vmware-vmkauthd-start
vmware-authd[4606]: Redirected mks to 192.168.12.6:903
xinetd[1317]: START: vmware-authd pid=4878 from=192.168.12.25
vmware-authd[4878]: login from 192.168.12.25 as 52f8c4f6-cec1-7a6a-bc17-b62774a0bc3d
vmware-authd[4878]: Found vmkauthd: /usr/lib/vmware/bin/vmware-vmkauthd-start
vmware-authd[4878]: Redirected mks to 192.168.12.6:903
snip
I tried the thing with vmauth.server.alwaysproxy = TRUE and also restarted vmware-vmkauthd.
But there is no service listening on port 903 and the error remains.
Any ideas? Kind regards
Cornelius
Hi,
Try restarting vmware-vpxa and mgmt-vmware service
regards
santhosh
Hi,
We have the exact same problem! The vm's are running fine, but we can't open the console. I've tried several restarts of the esx server, but it doesn't seem to work. The ESX servers are IBM X Series 3850. We have the exact same installation on some IBM blades, where there's no problem at all. Only these two 3850 seems to have the problem. Maybe it's a hardware issue?
Did you resolve this?
Thanks,
Rasmus
"service vmware-vpxa restart" worked like a charm. Thanks for the advice.
We're runing 3.0.2 patch levels for both ESX and VirtualCenter....admittedly behind on patches since 3.0.2....waiting to jump to 3.5. I wasn't able to open a console with VI Client through virtual center or byattaching directly to the host.
I had this problem with ESX servers and VM's open console. It was a DNS problem with my DNS server. Once I fixed the problem there I could open a console again.
What was the problem on your dns server?
I have this same problem also but it only is happening to certain Administrators. From my workstaion I can console to all the VM's but 1 or 2 of my Admins are not able to. I am wondering if this is more a bug within the client then DNS issue. Any thoughts?
I had all hosts files with the correct IP's and names. What it came down to was when I tried to connect to the console I could not open any of them. When I looked around to see what was causing the problem I noticed that DNS had the incorrect IP address to one of my ESX servers. Once I changed these addresses console access started working again.
The VirtualCenter server must be able to resolve the DNS-name <-> IP (and vice versa) as well as resolve the name shown in VirtualCenter (if used a non-FQDN) to the same result.
Additionaly there are some special requirements if your ESX's and VirtualCenter are seperated by a firewall....
Can you get console access if run VC client from the VC server?
Hi,
VI Client Cannot Open Remote Console Session on ESX Server 3.0
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=749640
--
Wil
