- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2019 11:29 AM
We've successfully Discovered vCenters w/in our firewall, but now need to do one outside our firewall.
To date, I requested to have the following ports opened, however, (Jakarta) Discovery is still failing, so am asking which ports must be opened for a successful credentialed Discovery?
TCP/22 - SSH
TCP/135 - WMi
TCP/445 - WMi
TCP/443 - vCenter
TCP 902 - vCenter
The expectation is we will start with the vCenter and then move on to a few stand-alone physical servers running Windows or UNIX.
Thanks.
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2019 05:42 AM
By default, the VMWare - vCenter Datacenters probe runs on port 443, which is the standard port for the https protocol. The port probes for vCenter run on these ports:
- vmapp6_https: 9443
- vmapp_https: 5480
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2019 07:33 AM
Thanks! I will go back to our firewall admin with this information and get them opened up and then retry Discovery of the vCenter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2025 12:17 AM
If you go for vCenter, which is the most complete discovery of all ESX hosts and VM instances in a VMware datacenter by connecting to just one IP, you will need 443 (for loading the data) but 5480 as well, because it is needed for classifying the IP as a vCenter... without it, discovery will not even try to log on.
Port 9443 was used up to vCenter version 6, it is not needed any more.
Port 902 was for single ESX servers without vSphere.
