VI Client error when trying to open a console for a VM

[anaghavartak]

Hi,

This is what I am trying to do. We have mulitple users who need access to VCenter Console and using Remote Desktop to connect to the VCenter server, we can have only 2 simultaneous active connections. One option is to use a Terminal server so that multiple people could access the Console. Instead of that route, I am trying to use the Virtual Infrastructure Client to connect to the console from the users desktop. So that once the VI Client is installed on users desktops they should be able to connect to the console wothout having to Remote Desktop into the VCenter Server.

When I try connecting, the console opens just fine and all options appear to work fine. However here is the issue: When I right click any VM and click "Open console", it opens a new iwndow and then either hangs and closes the window or displays an error message: "Error Connecting: Cannot connect to host <IP address>: A connection attempt faield because the connected party did not respond after a period of time, or established connection fialed because connected host failed to respond"

Any idea why this is happening? Is there some port that needs to be opened? or any other setting that needs to be edited?

Thanks in advance. Also my apologies if this is in the wrong section (but was unsure where else to put it)

[VMmatty]

Are you trying to access the remote console across two different subnets? And is there a firewall in between your PC and the ESX host?

You can try adding the following line to /etc/vmware/config and see if it helps:

vmauthd.server.alwaysProxy=TRUE

I've also seen this happen if the default gateway isn't set correctly on the Service Console port group.

[anaghavartak]

Well the server is behind a NAT firewall. The external IP is in the same subnet as my desktop (from which I am trying to open the remote console). I tired adding the line you mentioned but that did not help. Also the document on

suggested that port 903 needs to open, which I did open on the firewall, but that too did not work.

What does the gateway need to be and how can I edit it? Thanks

[nabsltd]

What version of ESX are you using? If the ESX server is managed by Virtual Center, what version of VC?

The ports that need to be opened are different for different versions, but for ESX3.5 and VC 2.5, you need the following:

ESX: ports 443, 902, and 903

VC: port 443

For earlier versions of VC, you will probably need:

ESX: ports 443, 902, and 903

VC: port 443, 902

[anaghavartak]

yes we are using ESX 3.5 u3 and VCenter 2.5 update3. The ports you mentioned for these versions have already been opened, but that still gave the same error.

[NickJBooth]

Hi

I had a similar issue and it was the local machine inability to resolve all the hosts names to IP addresses. I added manual entries for my hosts in my windows hosts file and that resolved it straight away

[anaghavartak]

I tired adding the entry in the host file, but that too does not seem to help. Also, the error message I receive says that it cold not connect to the <IP address> (not hostname). So I guess it already has resolved the IP address for the host it needs to connect to. Someone...help!!!

[polysulfide]

Need some more info here. Your workstation is on the same subnet as the external interface of your NAT firewall or your server? Can you describe the topology a bit more? If the server is behind the firewall, is there a one-to-one mapping or are there just forwarded ports? If the ports are forwarded, have you made sure to forward all of the ports that you opened?

Are you using the FQDN of your virtual center when you connect the VI client? Are you getting a certificate error when you connect?

Are you opening / forwarding these ports to each ESX server or just to the VC server? Is host name resolution for short and long name of the esx servers working from your workstation?

If it was useful, give me credit

Jason White - VCP