Last updated: 2026-03-31

Source: https://support.freshservice.com/support/solutions/articles/50000011874-discovery-port-configurations

Different discovery methods use different ports. Open only the required ports between the Remote Collector (RC) and target systems.

Restrict access to these ports using VLANs to ensure that only RCs can communicate with target systems and don't allow unrestricted access from all systems.

Agent-based discovery does not require these ports to be opened. Agents only need to communicate with the Remote Collector and do not need direct communication with the cloud. Direct cloud communication is optional but using an RC is recommended for controlled environments.

The following table provides a complete reference of ports that may be used to access target systems during discovery, including their direction of communication.

SourceDefault PortProtocolDirectionalityReason
Remote Collector(s) (RC)53 (TCP)DNSRC to targetsDNS Zone Discovery
Remote Collector(s) (RC)623 (UDP)IPMIRC to targetsIPMI based discovery of management interfaces
Remote Collector(s) (RC)22 (TCP)SSHRC to targetsSSH based discovery of Linux and Unix systems
Remote Collector(s) (RC)161 (UDP)SNMPRC to targetsSNMP discovery of network equipment and connections, and any management interfaces
Remote Collector(s) (RC)443 (TCP)APIs<br>SMISRC to targetsHypervisor, Cloud and Cisco ACI/UCS Discovery
Remote Collector(s) (RC)80/443 (TCP)<br>5988/5989 (TCP)APIsRC to targetsStorage Discovery
Windows Discovery Service (WDS)443 (TCP)HTTPSWDS to RCConnection from WDS to Remote Collector
Windows Discovery Service (WDS)135 (TCP)<br>137 (UDP)<br>139 (TCP)<br>445 (TCP)<br>1024-65535 (TCP)WMIWDS to targetsWMI based discovery of Windows infrastructure
Windows Discovery Service (WDS)5985 (TCP)<br>5986 (TCP)WinRMWDS to targetsWinRM discovery of Windows infrastructure