Documentation forSolarWinds Platform

SolarWinds Port Requirements

Updated: April 18, 2023

The following reference provides a comprehensive list of port requirements for SolarWinds products. The ports vary from product to product and on a per use basis. In some cases, ports are configurable. Refer to your product Administrator Guide for more information.

If you have installed one or more SolarWinds Platform products, make sure you review ports for the SolarWinds Platform and the features you use in addition to the ports required by your product.

SolarWinds Platform products

Ports for SolarWinds Platform features

Additional polling engine

Additional polling engines (APEs) have the same port requirements as the main polling engine. The following ports are the minimum required for an Additional polling engine to ensure the most basic functions.

Port Proto-
col
Service/
Process
Direction Description
161 UDP SolarWinds Job Engine Outbound The port used by the Additional polling engine (APE) to query for SNMP information on the device and to send it to the APE.
162 UDP SolarWinds Trap Service Inbound The port used by the APE for receiving trap messages from devices.

1433

TCP

SolarWinds Collector
Service
Outbound The port used for communication between the APE and the SolarWinds Platform database.
1434 UDP SQL Browse Service Outbound The port used for communication with the SQL Server Browser Service (SolarWinds Platform database) and the APE to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports.

5671

TCP

RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Additional polling engine to the main polling engine.

17777

TCP

SolarWinds Information
Service
Bidirectional

The port used for communication between the Additional polling engine and the main polling engine.

Additional web server

Port Protocol Service/Process Direction Description

80

TCP

World Wide Web Publishing Service Inbound

Default Additional polling engine port. Open the port to enable communication from your computers to the SolarWinds Platform Web Console.

If you specify any port other than 80, you must include that port in the URL used to access the SolarWinds Platform Web Console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the web console is http://192.168.0.3:8080.

443 TCP IIS Inbound The default port for https binding.

1433

TCP

SolarWinds Information Service Outbound

The port used for communication between the SolarWinds Platform server and the SQL Server. Open the port from your SolarWinds Platform Web Console to the SQL Server.

5671 TCP RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Additional web server to the main polling engine.

17777

TCP

SolarWinds Information Service Outbound

SolarWinds Platform module traffic. Open the port to enable communication from all polling engines (both main or additional) to the Additional web server, and from the Additional web server to polling engines.

SolarWinds Platform High Availability

Port Protocol Service/Process Direction Description
53 UDP SolarWinds High Availability Service outbound Used when failing over with a virtual hostname to update the virtual hostname's DNS entry and for periodic monitoring.
135 TCP SolarWinds High Availability Service bidirectional Used to remotely manage services including DHCP server or DNS server.
4369 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. They do not need to be open in additional polling engine pools.
5671 TCP

SolarWinds High Availability

bidirectional Port 5671 must be open into the HA pool with the main SolarWinds Platform server from all SolarWinds Platform servers.
17777 TCP SolarWinds Installer bidirectional Used when installing the standby server software.
25672 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. They do not need to be open in additional polling engine pools.

Network Atlas

Port

Protocol

Service/Process Direction

Description

17777 TCP SolarWinds Information Service Bidirectional Remote instances of Network Atlas require TCP on port 17777 to either the SolarWinds NPM or the SolarWinds EOC server.

SolarWinds Platform Agent

SolarWinds Platform Agent: Target computer

Port Protocol Service/
Process
Direction Description Communication
method
OS
22 TCP

sshd

Agent installer

Inbound

Used to install the agent on Linux/Unix computers through SSH and SFTP or SCP.

Either Linux/Unix
135
TCP

Agent installer

Inbound

(DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the target computer for remote deployment.

WMI is only needed for deploying the agent to a Windows server with the Add Node or Add Agent wizard. If you do not want to open WMI ports required for software deployment, you can use another deployment method for the Agent.

WMI also uses any random TCP port greater than 1024. See WMI portocalypse on THWACK.

Either Windows
445
TCP Agent installer

Inbound

Microsoft-DS SMB file sharing. This port must be open on the target computer (inbound) for remote deployment.

Either Windows
17778
TCP

SolarWinds Agent

Outbound

Used continuously by the agent to communicate back to theSolarWinds Platform server. Also used to deploy the agent. Agent-initiated

All

17790

TCP

SolarWinds Agent

Inbound

Used to communicate with the SolarWinds Platform server. Server-initiated All
Dynamic UDP SolarWinds.ServiceHost.Process.exe Outbound SolarWinds Cortex utilizes two dynamic UDP listening ports from dynamic range (assigned by OS) for SNMP polling. One port is for IPv4 and the second one is for IPv6 (if enabled). Either Windows

SolarWinds Platform Agent: SolarWinds Platform server

Port Protocol Service/
Process
Direction Description Communication
method
OS
22 TCP n/a

Outbound

Used to install the agent on Linux/Unix computers through SSH and SFTP or SCP.

Either Linux/Unix
17778
TCP

Orion Module Engine

SolarWinds Agent

Inbound

Used continuously by the agent to communicate back to the SolarWinds Platform server. Also used to deploy the agent. Agent-initiated

All

17790

TCP

Orion Module Engine

SolarWinds Agent

Outbound

Used to communicate with the SolarWinds Platform server. Server-initiated All

SolarWinds Platform Agent: Local ports

The following ports are required for local communication inside the server or agent. Do not open them in the firewall; they are used only by local services.

Port Protocol Direction Description
17775 TCP Inbound (on agents) RestAPI forwarder for Cortex
17798 TCP Inbound (on servers) Cortex Diagnostics API
Dynamic TCP Inbound (on agents) Port used for communication between the JobEngine and its workers.

SolarWinds Installer

Port Protocol Service/Process Direction Description

80

HTTP

Installer (SolarWinds Administration Service) Outbound Used when installation data are transferred from the main polling engine to Additional polling engine (depending on the SolarWinds Platform configuration).
443 HTTPS Installer (SolarWinds Administration Service)

Inbound (online installer)

Outbound (when data are downloaded from the main polling engine to Additional polling engines)

Used by the online installer when data are downloaded from the Internet. It can also be used when installation data are transferred from the main polling engine to Additional polling engines.
17777 WCF

SolarWinds Administration Service

Bidirectional

Used for the communication between polling engines, also used as a fallback option when HTTP/HTTPS fails to download data to Additional polling engine.

Database Performance Analyzer Integration Module (DPAIM)

 

Engineer's Toolset (ETS)

Engineer's Toolset on the Desktop

 

Engineer's Toolset on the Web

 

Enterprise Operations Console (EOC)

 

IP Address Manager (IPAM)

 

Log Analyzer

 

NetFlow Traffic Analyzer (NTA)

 

Network Configuration Manager (NCM)

 

Network Performance Monitor (NPM)

NPM ports

  • Ports 4369, 25672, and 5671 are opened by default on the main server for RabbitMQ messaging. These ports can be blocked by the firewall. When running SolarWinds High Availability, ensure ports 4369 and 25672 are open.
  • RPC ports > 1024 (TCP, bidirectional) is used by the Job Engine v2 process to communicate with Windows nodes.

SolarWinds does not recommend the use of HTTP (Port 80). Please use HTTPS (Port 443) to ensure that any web-related connections are secure.

Port Protocol Service/Process Direction Description Encryption
user-defined, default: 22 SSH

SolarWinds Job Engine v2

IIS

Outbound from the SolarWinds Platform server to the device Port for accessing ASA devices through CLI Device-based

25

TCP

SolarWinds Alerting Service V2 Outbound

SMTP port for non-encrypted messages

n/a
53 UDP SolarWinds Job Engine v2 Bi-
directional
Resolving DNS queries n/a

80

TCP

IIS Inbound

HTTP default for the SolarWinds Platform Web Console website.

If you specify any port other than 80, you must include that port in the URL used to access the SolarWinds Platform Web Console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the web console is http://192.168.0.3:8080.

The port might also be used for Cisco UCS monitoring.

No
135 TCP Microsoft EPMAP (DCE/RPC Locator service) Bi-
directional
Required for devices polled via WMI. Used to initiate communication with the remotely managed host.  

161

UDP

SolarWinds Job Engine v2

SolarWinds Cortex

Bi-
directional

Send and receive SNMP
information

SNMP v1 and v2 are unencrypted. SNMP v3 uses AES and 3DES encryption.

162

UDP

SolarWinds Trap Service

SNMP Informs

Inbound

Receive trap messages

n/a

443

TCP

IIS Inbound

Default port for https binding.

SSL

465

TCP

SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions

SSL

514

UDP

SolarWinds Syslog Service Inbound

Receive syslog messages

n/a

587

TCP

SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions

TLS

1433

TCP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound

Communication between the SolarWinds Platform server and the SQL Server.

n/a

1434

UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

SQL Server Browse Service

Outbound

Communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports.

n/a

5671

TCP

RabbitMQ

Bi-
directional

For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all SolarWinds Platform servers (additional polling engines, HA servers, or additional web servers).

Sending messages to RabbitMQ.

TLS 1.2

17777

TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex

Bi-
directional

Communication between services and SolarWinds Orion module traffic.

Communication between the SolarWinds Platform Web Console and the polling engines.

Communication between the main server and pool members.

RSA handshake, AES 256 communication using WCF

TLS 1.2 with Cortex

17774

HTTPS

SolarWinds REST Endpoint Inbound to the SolarWinds Platform server

Required for access to the SWIS API.

SolarWinds recommends that you start using port 17774 instead of 17778.

SSL

17778

HTTPS

SolarWinds Agent Inbound to the SolarWinds Platform server

Required for agent communication.

SSL

Optional, individual components, such as SolarWinds Platform Agents and High Availability, have additional port requirements.

NetPath™ ports

 

Other firewall settings for NetPath

 

Patch Manager

 

Server & Application Monitor (SAM)

SAM ports

 

Container monitoring

Port Protocol Service/Process Direction Description
38012 HTTPS

Container Monitoring

Bidirectional Communication between the Orion Business Layer and container environments

Additional port requirements for container services include:

  • For Docker and Docker Swarm:
    • 80: Used to download the configuration file from the SolarWinds Platform server
    • 4043: Container port (internal Docker communication)
    • 6784: Report status (internal Docker communication)
  • For Kubernetes (K8s) and Microsoft Azure Kubernetes (AKS):
    • 4043: Target port/Container port (internal Docker communication)
    • 10250: Listening port for Kubelet agent
    • 30043: Node port (internal Docker communication)
  • For Apache Mesos:
    • 4043: Mesos master server port (internal Mesos communication)
    • 8080: Deployment service (internal Mesos communication)

Nutanix

Port Protocol Service/Process Direction Description Encryption
22 SSH SolarWinds Job Engine v2 Outbound

The port used for Nutanix hardware health monitoring.

 
9440 HTTPS and TCP SolarWinds Cortex Bidirectional Communication between polling engines and the Nutanix AOS API. TLS 1.2

Server Configuration Monitor (SCM)

 

Storage Resource Monitor (SRM)

 

User Device Tracker (UDT)

 

Virtualization Manager (VMAN)

VMAN ports

 

Container monitoring

Port Protocol Service/Process Direction Description
38012 HTTPS

Container Monitoring

Bidirectional Communication between the Orion Business Layer and container environments

Additional port requirements for container services include:

  • For Docker and Docker Swarm:
    • 80: Used to download the configuration file from the SolarWinds Platform server
    • 4043: Container port (internal Docker communication)
    • 6784: Report status (internal Docker communication)
  • For Kubernetes (K8s) and Microsoft Azure Kubernetes (AKS):
    • 4043: Target port/Container port (internal Docker communication)
    • 10250: Listening port for Kubelet agent
    • 30043: Node port (internal Docker communication)
  • For Apache Mesos:
    • 4043: Mesos master server port (internal Mesos communication)
    • 8080: Deployment service (internal Mesos communication)

Nutanix

Port Protocol Service/Process Direction Description Encryption
22 SSH SolarWinds Job Engine v2 Outbound

The port used for Nutanix hardware health monitoring.

 
9440 HTTPS and TCP SolarWinds Cortex Bidirectional Communication between polling engines and the Nutanix AOS API. TLS 1.2

VoIP & Network Quality Manager (VNQM)

 

Web Performance Monitor (WPM, formerly SEUM)

 

Other SolarWinds products

Access Rights Manager (ARM)

 

Dameware (DRS, MRC, DRE)

Dameware centralized

 

Dameware stand-alone

 

Dameware Remote Everywhere

 

Database Performance Analyzer (DPA)

 

ipMonitor

 

Kiwi CatTools

 

Kiwi Syslog Server

 

Network Topology Mapper (NTM)

 

Security Event Manager (SEM)

 

Serv-U File Server

 

Web Help Desk (WHD)