VI 3 Client ports

[PatrickWE]

Wondering what ports are needed to be open to access a internal ESX 3.0.1 server using VI3 client.

Is there a more secure way, beside a VPN connection to access an internal ESX server ???

Thanks \!!!

[kimono]

Here's a good thread on the matter:

http://www.vmware.com/community/thread.jspa?threadID=46386

Which has some good links to documentation also.

kimono

[Dave_Mishchenko]

You'll need to open 902 for the VI3 client ond 903 if you're using the VM console.

This thread discusses other threads. You may consider putting the console connection for your server on an isolated LAN to prevent general access to the server.

http://www.vmware.com/community/thread.jspa?messageID=621890&tstart=0

[PatrickWE]

I'm trying to configure the ports in these treads ( 902 & 903 ) trough an ISA 2004 server, but still no luck...

I have opened TCP Inbound 902 ( server publishing )

and secondary connection 902 UDP Both direction and 903 TCP inbound...

Can anyone tell me what am I missing, since it's not working...

I just need the VI client and VM console to work trough this firewall, no need for other stuff...

Thanks \!!!

[bflynn0]

If you're connecting your VIClient straight to the ESX Server you'll need the following open inbound to the ESX Server:

80/tcp

443/tcp

902/tcp

903/tcp

If you're connecting your VIClient to a VirtualCenter server you'll need the following:

Inbound to the VC Server:

80/tcp

443/tcp

902/tcp

905/tcp (If your VC Server is configured for legacy support)

Inbound to the ESX Server:

903/tcp

[PatrickWE]

Ok, the VI client now connects, but not the console...

I have all the ports specified incoming ( TCP 80, 443, 902, 903 ) and outgoing ( TCP 902, 903, UDP 902, 903 )...

Getting connection error when trying to open a Console on any VM...

Thanks for any help anyone can provide...

[bflynn0 · Accepted solution]

if the ESX Server is being NAT'ed (i.e. the IP Address you connect to is not the same IP Address that is on the ESX Service Console), you'll need to add the following to /etc/vmware/config[/b] on the ESX host:

vmauthd.server.alwaysProxy=TRUE

[MrEHere]

If all the right ports are opened and the VI3 client connects - BUT you can not console via the VI3 client - I found that this may be a name resolution issue. Ensure that your ESX hosts are properly registered in DNS. As a test/work around, you can enter the FQDN's into the host file on the computer the VI3 client is running from.