Thank you so much for looking at my. I am trying to open up ports 443 and 80 for access to the vCenter server by a disaster recovering software. The disaster recovery site is located in the different state and we have vpn tunnel between two sites with ports 443 & 80 open. The disaster recovery site is an esx host 5.0.
I ran nmap ping to check on ports 443 & 80 to esx host:
Port 443
Starting Nmap 6.40 ( http://nmap.org ) at 2013-10-10 11:26 Central
Daylight Time Nmap scan report for xxx.xxx.xx.xx Host is up (0.0079s
latency). PORT STATE SERVICE
443/tcp open httpsNmap done: 1 IP address (1 host up) scanned in 24.41 seconds
Port 80
Starting Nmap 6.40 ( http://nmap.org ) at 2013-10-10 11:27 Central
Daylight Time Nmap scan report for xxx.xxx.xx.xx Host is up (0.0098s
latency). PORT STATE SERVICE
80/tcp open httpNmap done: 1 IP address (1 host up) scanned in 13.52 seconds
Now, when I do the same thing for vCenter, I get this:
Port 443
Starting Nmap 6.40 ( http://nmap.org ) at 2013-10-10 11:12 Central
Daylight Time Nmap scan report for xxx.xxx.xx.xx Host is up (0.0078s
latency). PORT STATE SERVICE 443/tcp closed httpsNmap done: 1 IP address (1 host up) scanned in 7.11 seconds
Port 80
Starting Nmap 6.40 ( http://nmap.org ) at 2013-10-10 11:13 Central
Daylight Time Nmap scan report for xxx.xxx.xx.xx Host is up (0.0079s
latency). PORT STATE SERVICE 80/tcp closed httpNmap done: 1 IP address (1 host up) scanned in 6.38 seconds
I also attempted to run esxcfg-firewall –openPort ,tcp|udp,in|out, to open up the ports, but I don't believe this command applies to esx 5.0.
I know I might be missing some important info, so please, please, ask follow ups.
Thank you!!!
Best Answer
Erm....this is an odd one.
What are you trying to achieve and why? Are you aware that vCenter itself uses both 80 and 443? you know that vCenter talks to its hosts via 902/903 right?
Have you seen THIS?