Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Port requirements for all SolarWinds products

Port requirements for all SolarWinds products

Updated: March 14, 2017

For a PDF of this article, click the PDF icon under the Search bar at the top right of this page.

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.

Additional Polling Engines

Additional Polling Engines have the same port requirements as Main Polling Engine. The following ports are the minimum required for an Additional Polling Engine to ensure them most basic functions.

Port

Protocol

Service/
Process
Direction

Description

1433

TCP

SolarWinds Collector Service Outbound The port used for communication between the APE and the Orion database.
1801 TCP Message Queuing WCF Inbound The port used for MSMQ messaging from the Orion Web Console to the Additional Polling Engine.

5671

TCP

RabbitMQ Bidirectional

The port used for SSL-encrypted RabbitMQ messaging from the Orion Web Console to the Additional Polling Engine.

17777

TCP

SolarWinds Information Service Bidirectional

The port used for communication between the Additional Polling Engine and the Orion Web Console.

Additional Web Servers

Port

Protocol

Service/Process Direction

Description

80

TCP

World Wide Web Publishing Service Inbound

Default additional web server port. Open the port to enable communication from your computers to the Orion Web Console.

If you specify any port other than 80, you must include that port in the URL used to access the 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 .

1433

TCP

SolarWinds Collector Service Outbound

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

1801 TCP Message queuing Outbound The port used for MSMQ messaging from the Additional Web Server to the Primary Polling Engine.
5671 TCP RabbitMQ Outbound The port used for SSL-encrypted RabbitMQ messaging from the Additional Web Server to the Additional Polling Engine.

17777

TCP

SolarWinds Collector Service Outbound

Orion module traffic. Open the port to enable communication from your polling engine to the web server, and from the web server to your polling engine.

Database Performance Analyzer (DPA)

Port Protocol Service or Process Direction Encryption Description
8123 HTTP

Windows: Ignite PI Service

Linux: java/tomcat

Inbound

Outbound

  Default HTTP port for web server
8124 HTTPS

Windows: Ignite PI Service

Linux: java/tomcat

Inbound

Outbound

TLS 1.0

TLS 1.1

TLS 1.2

Default HTTPS port for web server
8127 TCP

Windows: Ignite PI Service

Linux: java/tomcat

Internal   Internal Tomcat shutdown port
80 HTTP

Windows: Ignite PI Service

Linux: java/tomcat

Inbound

Outbound

  Default HTTP port for web server (Amazon Machine Images only)
443 HTTPS

Windows: Ignite PI Service

Linux: java/tomcat

Inbound

Outbound

TLS 1.0

TLS 1.1

TLS 1.2

Default HTTPS port for web server (Amazon Machine Images only)

Database Performance Analyzer Integration Module (DPAIM)

In addition to the port requirements necessary for SolarWinds DPA and your Orion platform product, integration requires the following ports:

DPA server

Port Protocol Service or Process Direction Encryption Description

443 (cloud) or

8124 (on-premises)

TCP (HTTPS)

Windows: Ignite PI Service

Linux: java/tomcat

Inbound

Outbound

TLS 1.0

TLS 1.1

TLS 1.2

This is the default port number of your DPA website and jSWIS proxy.

This port must be open to receive data from the SolarWinds Orion server.

Orion server

Port Protocol Service or Process Direction Description
17776 TCP SolarWinds Information Service

Inbound

Outbound

This port must be open to access the SolarWinds Information Service API (notifications).
17777 TCP

SolarWinds Information Service

SolarWinds Orion Module Engine

Inbound

Outbound

This port must be open for all Orion platform product traffic.
17778 TCP SolarWinds Information Service

Inbound

Outbound

This port must be open to access the SolarWinds Information Service API.

Engineer's Toolset (ETS)

The following lists the required ports needed for the Engineer's Toolset.

Component

Port

Type

Description

Syslog Server

514

UDP

Allows you to listen for incoming Syslog messages on UDP port 514.

WAN Killer

7
9

 

Use port 7 to generate traffic going both ways. When data is sent to port 7 (echo), all traffic that is received by the target device will be sent back to WAN Killer. This will generate a load in both directions.

Use port 9 (discard) to generate one-way traffic. Port 9 discards all data when received.

Netflow Realtime

2055

 

Listens on Port 2055

TFTP Server

69

UDP

 

SNMP Polling

161

 

 

Sending emails

25

 

 

Web Toolset

  • Uses port 443 for Secured SSH Connection.

Enterprise Operations Console (EOC)

Port Protocol Service or Process Direction Component Encryption Description
80 TCP IIS (w3wp.exe) Bidirectional Website No HTTP default for the Orion Web Console
443 TCP IIS (w3wp.exe) Bidirectional Website SSL/TLC HTTPS default for the Orion Web Console
17777 TCP SolarWinds Information Service Bidirectional SWIS Certificate (SHA) Used for the SolarWinds Information Service (SWIS) protocol

Firewall Security Manager (FSM)

Port

Type

Component

Comment

17778

 

 

For the NCM repository import method. FSM connects on this port to the Orion information service on the primary polling engine.

18184

TCP

 

For network connectivity between the Check Point management server and the FSM server.

18210

TCP

FW1_Ica_pull (the Check Point internal CA pull service)

 

18190

TCP

CPMI service

 

18191

TCP

Check Point Daemon (CPD)

 

21, 22 

Telnet/SSH 

 

For direct connection to firewalls to gather configs

3050

TCP

Firebird Database Manager

OFSMM, FSM server and FSM Client communication with Firebird DB

4568

TCP

License Manager Listener

 

45680

TCP

License Manager Service

 

48080

HTTP

FSM Web Server

 

17784

HTTPS

Orion FSM Web Service

 

High Availability 

Port Protocol Service/
Process
Direction Description
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 Orion server from all Orion servers.
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.

IP Address Manager (IPAM)

Port 53 (TCP) for zone transfers (DNS record polling).

ipMonitor

ipMonitor uses the following local Ports:

  • HTTP Port (default is 8080 and TCP 443 for SSL or administrator assigned).

The following table provides the various ports that are utilized depending on which monitor is enabled.

Monitor

Type

Port

Parent Protocol

ACTIVE DIRECTORY 

Active Directory

389

TCP

BANDWIDTH USAGE

Bandwidth

161

UDP

BATTERY

Battery

161

UDP

CPU USAGE

Processor Usage

161

UDP

DIRECTORY MONITOR

Directory Usage

n/a

SMB or NFS

DNS-QA

Quality Assurance Domain Name Service

53

TCP

DNS-TCP

Domain Name Service - Transmission Control Protocol

53

TCP

DNS-UDP

Domain Name Service - User Datagram Protocol.

53

UDP

DRIVE SPACE

Drive Space Availability

161

UDP

EVENT LOG

NT Event Log Monitor

n/a

n/a

EXCHANGE SERVER

Microsoft® Exchange Server

n/a

n/a

EXTERNAL PROCESS

Executable File

n/a

n/a

FAN MONITOR

Fan Status

161

UDP

FILE PROPERTY

Any File Type

n/a

SMB or NFS

FILE WATCHING

Any File Type

n/a

SMB or NFS

FINGER

Finger Information Server

79

TCP

FTP

File Transfer Protocol

21

TCP

FTP-QA

Quality Assurance File Transfer Protocol

21

TCP

GOPHER

Menu driven front end to resource services such as anonymous FTP

70

TCP

HTML / ASP 

HyperText Transfer Protocol

80

TCP

HTTP

HyperText Transfer Protocol

80

TCP

HTTP-QA

Quality Assurance HyperText Transfer Protocol

80

TCP

HTTPS

Hypertext Transfer Protocol Secure

443

TCP

HUMIDITY

Humidity Levels

161

UDP

IMAP4

Internet Message Access Protocol

143

TCP

IMAP4-QA

Quality Assurance Internet Message Access Protocol

143

TCP

IPMONITOR

ipMonitor

80, 443 

TCP

IRC

Internet Relay Chat

6667

TCP

KERBEROS 5

Kerberos 5

88

UDP

LDAP

Lightweight Directory Access Protocol

389

UDP

LINK-QA

Quality Assurance Link

80

TCP

LOTUS NOTES

Lotus NotesTM Transport

1352

TCP

MAPI-QA

Microsoft Messaging Application Program Interface

n/a

n/a

MEMORY USAGE

Physical Memory (RAM)

161

UDP

NETWORK SPEED 

Speed or Bandwidth Monitor

19

TCP

NNTP

Network News Transfer Protocol

119

TCP

NTP

Network Time Protocol

123

UDP

PING

Packet InterNet Groper

n/a

ICMP

POP3

Post Office Protocol

110

TCP

POP3-QA

Quality Assurance Post Office Protocol

110

TCP

RADIUS

Remote Authentication Dial-In User Service protocol

1812

UDP

RWHOIS

Recursive WhoIs Information Server

4343

TCP

SERVICE

Windows NT Service Monitor

n/a

NT Specific

SMTP

Simple Mail Transfer Protocol

25

TCP

SNMP

Simple Network Management Protocol

161

TCP

SNMP-QA

Quality Assurance Simple Network Management Protocol

161

UDP

SNMP TRAP-QA

Simple Network Management Protocol Traps

162

UDP

SNPP

Simple Network Pager Protocol

444

TCP

SQL: ADO

Structured Query Language: ActiveX Data Objects

n/a

NT Specific

SQL: ADO-QA

Structured Query Language: ActiveX Data Objects

n/a

NT Specific

SQL SERVER

Structured Query Language Server

n/a

NT Specific

TELNET

Remote Terminal Protocol

23

TCP

TEMPERATURE

Temperature Levels

161

UDP

WHOIS

WhoIs Information Server

43

TCP

ipMonitor Traps

Any agent you configure to send Traps to ipMonitor must use this same IP Address and Port combination.

If the Windows SNMP Trap Service is enabled on the ipMonitor host computer, it is very likely to conflict with ipMonitor's SNMP Trap Listener. Both are bound by default to port 162.

The POP3 User Experience monitor delivers an email to the SMTP server on port 25 for the recipient address you specify. The monitor then logs in to the POP3 Mail Server on port 110 and retrieves the LIST of queued mail.

Kiwi Syslog Server

Kiwi Syslog Server uses the following ports.

Port Protocol Used for
514 (default), plus one Ephemeral port UDP Incoming UDP messages
1468 (default) TCP Incoming TCP messages

162 (default) for IPv4

163 (default) for IPv6

UDP

Incoming SNMP traps

6514 (default) TCP Incoming secure TCP messages
3300, plus one Ephemeral port TCP Internal communication between the Syslog service and Syslog Manager
8088 (default) TCP Kiwi Syslog Web Access

Versions of Kiwi Syslog Server prior to 9.2.1 were installed with the Ultidev Cassini Web Server Explorer, which used an additional port TCP 0.0.0.0:7756. Cassini Web Server Explorer (and this port) are no longer used.

LANsurveyor

To ensure that LANsurveyor scans thoroughly, turn on file and print sharing services and configure your workstation firewall to allow connections to UDP 137, UDP 138, UDP 445, and TCP 139, and TCP 445 ports.

Log & Event Manager (LEM)

Port # Protocol Service Direction Description
22, 32022 TCP SSH Bidirectional SSH traffic to the SolarWinds LEM VM. (Port 22 is not used prior to version 6.3.x.)
25 TCP SMTP Outbound SMTP traffic from the SolarWinds LEM VM to your email server for automated email notifications.
80, 8080 TCP HTTP Bidirectional Non-secure HTTP traffic from the SolarWinds LEM Console to the SolarWinds LEM VM. (LEM closes this port when activation completes, but you can re-open it with the CMC togglehttp command.)
139, 445 TCP NetBIOS, SMB Bidirectional

Standard Windows file sharing ports (NetBIOS Session Service, Microsoft SMB) that LEM uses to export debug files, syslog messages, and backup files.

The LEM Remote Agent Installer also uses these ports to install agents on Microsoft Windows hosts across your network.

161, 162 TCP SNMP Bidirectional SNMP trap traffic received from devices, and used by Orion to monitor LEM. (Monitoring LEM on port 161 is not used prior to version 6.3.x.)
389, 636 TCP  LDAP Outbound

LDAP ports that the LEM Directory Service Connector tool uses to communicate with a designated Active Directory domain controller.

The LEM Directory Service Connector tool uses port 636 for SSL communications to a designated Active Directory domain controller.

443, 8443 TCP HTTPS Bidirectional

HTTPS traffic from the SolarWinds LEM Console to the LEM VM.

LEM uses these secure HTTP ports after LEM is activated.

(445) TCP     See entry for port 139.
514 TCP or UDP Syslog Inbound Syslog traffic from devices sending syslog event messages to the SolarWinds LEM VM.
(636) TCP     See entry for port 389.
2100 UDP NetFlow Inbound NetFlow traffic from devices sending NetFlow to the SolarWinds LEM VM.
6343 UDP sFlow Inbound sFlow traffic from devices sending sFlow to the SolarWinds LEM VM.
(8080) TCP     See entry for port 80.
(8443) TCP     See entry for port 443.
8983 TCP nDepth Inbound nDepth traffic sent from nDepth to the LEM VM containing raw (original) log data. 
9001 TCP LEM Reports Bidirectional LEM Reports traffic used to gather LEM Reports data on the LEM VM.
(32022) TCP     See entry for port 22.
37890-37892 TCP LEM Agents Inbound LEM Agent traffic sent from SolarWinds LEM Agents to the SolarWinds LEM VM. (These ports correspond to the destination ports on the LEM VM.)
37893-37896 TCP LEM Agents Outbound LEM Agent return traffic sent from the SolarWinds LEM VM to the SolarWinds LEM Agents. (These ports correspond to the destination ports on the LEM agents.)

Note: LEM no longer uses the port listed in the following table.

Port # Protocol Service Direction Description
5433 TCP LEM Reports Inbound Port 5433 is no longer used. Previously, this port carried traffic from SolarWinds LEM Reports to the SolarWinds LEM VM. This was used by versions prior to LEM 5.6, for which support ended December 2015.

In LEM 6.2 and later, LEM will need access to the following URL to use the automatic connector update function and the Threat Feeds function:

  • https://rules.emergingthreats.net/fwrules/

Netflow Traffic Analyzer (NTA)

The following table lists ports that SolarWinds NetFlow Traffic Analyzer uses to communicate with other devices and servers.

Port Protocol Service/Process Direction Description
80 TCP World Wide Web Publishing Service Bidirectional Port used for web console and any other web servers.
137 UDP NetBIOS Outbound

Port for outbound traffic if NetBIOS name resolution is turned on.

When NTA is trying to resolve the NetBIOS names of servers in their conversations, you may find a large amount of outbound UDP 137 traffic from the NTA collector to a number of external addresses. You can confirm the traffic by using the Flow Navigator to match the outbound connections to existing conversations.

This is normal behavior when NetBIOS is enabled. An easy way to demonstrate the behavior is to disable NetBIOS in NTA and watch all outbound connections terminate.

161

UDP

SolarWinds Job Engine v2 Birdirectional Port used for sending and receiving SNMP information, including polling CBQoS-enabled devices.
1433 TCP SolarWinds Collector Service Outbound Port used for communication between the NTA Flow Storage Database and the existing SQL server.
2055 UDP SolarWinds Collector Service Inbound Port for receiving flows on any SolarWinds NTA collector.
5671 TCP RabbitMQ Bidirectional Rabbit MQ messaging.
17777 TCP SolarWinds Information Service Bidirectional

Port for sending and receiving traffic between SolarWinds NPM and other Orion Modules.

Port used for communication between remote Flow Storage Database and NTA Main Poller.

17778 HTTPS and TCP SolarWinds Information Service Bidirectional Open to access the SolarWinds Information Service API and agent communication.
17791 TCP SolarWinds Agent Bidirectional Open for agent communication on any SolarWinds Orion server running Windows Server 2008 R2 SP1.
Device-specific       Any port required by a specific device.

For a complete list of the port requirements for the SolarWinds Orion server, see the Port Requirements document.

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.

Network Configuration Manager (NCM)

The following ports may be needed for the Orion Web Console, depending on how SolarWinds NCM is set up to download and upload configurations:

Port Type Description
22 SSH/SCP

Default port for NCM to transfer configs

23 Telnet Default port for NCM to transfer configs
25 TCP SMTP email default that NCM uses for notification (If SSL/TLS encryption is set up on SMTP server, default port is 465)
69 UDP TFTP server listens on this port
80 TCP HTTP default for the Orion Web Console
161 UDP SNMP statistics collection, the default for polling in NCM
162 UDP Trap messages listened for and received by the Trap Server
443 TCP Default port for HTTPS binding.
465 TCP The port used for SSL-enabled email alert actions
514 UDP Syslog Service listens for incoming messages
587 TCP The port used for TLS-enabled email alert actions
1801 TCP

MSMQ WCF binding (For more information see this article from Microsoft)

5671 TCP For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers
17777 TCP Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion Web Console to your poller. The port used for communication between the Orion Web Console and the poller.
17778 HTTPS Required for access to the SWIS API and agent communication
17779 HTTP SolarWinds Toolset Integration over HTTP

Ports 4369, 5672, and 25672 are opened by default. These ports can be blocked by the firewall.

Network Performance Monitor (NPM)

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

 

Port Protocol Service/
Process
Direction Description Encryption

25

TCP

SolarWinds Alerting Service V2 Outbound

SMTP port for non-encrypted messages

n/a
53 UDP SolarWinds Job Engine v2 Outbound Resolving DNS queries n/a

80

TCP

IIS Inbound

Default additional web server port. If you specify any port other than 80, you must include that port in the URL used to access the 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. Open the port to enable communication from your computers to the Orion Web Console.

The port might also be used for Cisco UCS monitoring.

n/a

161

UDP

SolarWinds Job Engine v2 Outbound

Sending and receiving SNMP information.

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

162

UDP

SolarWinds Trap Service Inbound

Receiving trap messages

n/a

443

TCP

IIS Inbound

Default port for https binding.

Also used for bi-directional ESX/ESXi server polling, or for Cisco UCS monitoring.

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

Receiving 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

The port used for communication between the SolarWinds server and the SQL Server. Open the port from your Orion Web Console to 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

Outbound

The port used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations.

n/a

1801

TCP

MSMQ Bidirectional

MSMQ WCF binding 

WCF

5671

TCP

RabbitMQ Bidirectional

For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers.

TLS

17777

TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

Bidirectional

Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion Web Console to your poller. Used for communication between services.

The port used for communication between the Orion Web Console and the poller.

Used for communication between the main server and pool members.

RSA handshake, AES 256 communication using WCF

17778

HTTPS

SolarWinds Agent Inbound to the Orion server

Required for access to the SWIS API and agent communication

SSL

 

NetPath™

Open the following ports on your firewall for network connectivity used by NetPath™.

You may also need to open the following ports:

  • NPM ports for communication between polling engines.
  • Agent ports when deploying probes on remote machines using agents.

 

Port Proto-
col
Service or Process Direction Source Destination Description

11

(ICMP Time Exceeded)

ICMP SolarWinds Agent or JobEngineWorker Incoming Networking devices along your path NetPath™ probe Used by the NetPath™ probe to discover network paths.
User configured TCP SolarWinds Agent or JobEngineWorker Outgoing NetPath™ probe Endpoint service

Any ports of the monitored services that are assigned to the probe.

Used by the NetPath™ probe to discover service status.

43

443

TCP

SolarWinds.Business-LayerHost

(Main server only)

Outgoing Main polling engine

BGP data providers and announcements, such as:

Used by NetPath™ to query BGP information about the discovered IP addresses.

Network Topology Mapper (NTM)

PORT PROTOCOL SERVICE OR PROCESS DIRECTION DESCRIPTION
161 UDP SolarWinds Network Topology Job Scheduler Bidirectional Port used for SNMP statistics collection.
443 TCP SolarWinds Network Topology Job Scheduler Bidirectional

Port used to communicate with VMware Virtual Center or ESX server.

17778 HTTPS SolarWinds Network Topology Job Scheduler Outbound Port used to access the SolarWinds Information Service (SWIS) API for exporting maps from a scheduled discovery to Network Atlas.
1024 and 65535 TCP/UDP SolarWinds Network Topology Job Scheduler Bidirectional WMI communications use a port between 1024 and 65535. See Microsoft Windows specifications.
Create firewall exceptions to allow TCP/UDP traffic on ports 1024 - 65535 to enable mapping monitored objects that use WMI.

Orion Agents

Target computer

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

Inbound

Either Linux

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

135 TCP

Agent installer

Inbound

Either Windows (DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the target computer for remote deployment.
445 TCP Agent installer

Inbound

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

SolarWinds Agent

Outbound

Agent-initiated

Windows

Linux

Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.

17790

TCP

SolarWinds Agent

Inbound

Server-initiated All Used to communicate with the Orion server.
17791 TCP

SolarWinds Agent

Agent installer

Outbound

 

Agent-initiated Windows 2008 R2 Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.

Orion server

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

Outbound

Either Linux

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

17778 TCP

Orion Module Engine

SolarWinds Agent

Inbound

Agent-initiated

Windows

Linux

Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.

17790

TCP

Orion Module Engine

SolarWinds Agent

Outbound

Server-initiated All Used to communicate with the Orion server.
17791 TCP

Orion Module Engine

SolarWinds Agent

Inbound

Agent-initiated Windows 2008 R2 Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.

Patch Manager

Port Type Description
135 TCP (RPC Endpoint Mapper) The Patch Manager server uses this port to establish WMI connections to remote computers. It also uses this port to connect to the Service Control Manager (SCM) when it provisions the WMI providers dynamically on the remote computer.
389 TCP (Lightweight Directory Access Protocol) Patch Manager servers use this port for Active Directory authentication.
445 TCP (SMB over TCP) The Patch Manager server uses this port when it provisions the WMI providers to a remote computer.
4092 TCP

(Console-to-Server Communication) The Patch Manager console uses this port to communicate to an independent Patch Manager application server. This is a one-way communication channel that only requires inbound TCP traffic on the application server.

In a distributed environment, Patch Manager servers use this port in the same manner for "downstream" communication. For example, the Patch Manager Primary Application Server (PAS) uses port 4092 to communicate with remote Patch Manager servers in secondary server roles.

8787 TCP (Web Console Connections) By default, users connect to the Patch Manager web console server on port 8787.
17777 TCP (SolarWinds Information Service) The SolarWinds Information Service (SWIS) facilities data exchange for the Patch Manager Web Console, along with the web console Application Programing Interface (API). Ensure this port is not blocked on servers running the Patch Manager Web Console server.
1024-65536 Dynamic Ports (DCOM or RPC) Windows Management Instrumentation (WMI) technology is based on Distributed Component Object Model (DCOM)/RPC communication. DCOM/RPC allocates the ports used by the server within a dynamic port range. This range is typically between 1024 and 65536. To configure these ports using Windows Firewall on your managed computers, enable the Inbound Rules in the Windows Management Instrumentation (WMI) group.

Server & Application Monitor (SAM)

Review and open ports for SAM to support communication for the main polling engine, Orion SQL server, additional polling engines, web server, and additional web server. These ports include feature specific requirements including Orion agents, High Availability, and component monitors and templates.

Ports 4369, 25672, and 5672 are opened by default. These ports can be blocked by the firewall.

Port Type Direction

Encryption

Description
25 TCP     SMTP port for non-encrypted messages
161 UDP bidirectional   Statistics collection
162 UDP incoming   Trap Server listening for incoming messages
443 TCP bidirectional   Default port for https binding and bi-directional ESX/ESXi server polling and for Cisco UCS monitoring.
465 TCP outbound SSL SSL-enabled email alert actions
587 TCP outbound TLS TLS-enabled email alert actions
1801 TCP   WCF MSMQ WCF binding
4369 TCP bidirectional   Required for RabbitMQ messaging (epmd)
5671 AMQP bidirectional TLS SSL encrypted RabbitMQ messaging from the additional polling engines to the main polling engine
5672 TCP     Non-encrypted RabbitMQ messaging between the primary and additional polling engines. This is a backup communication port that is not used by default.
25672 TCP bidirectional   Required for RabbitMQ messaging (Erlang distribution)
17777 TCP bidirectional RSA handshake, AES 256 communication using WCF

Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion Web Console to your poller.

High Availability Service. Used for communication between the main server and pool members.

Job Engine V2, Collector Service, Business Layer, and Information Service v2,23. Used for communication between the services.

The port used for communication between the Orion Web Console and the poller.

17778 HTTPS and TCP   SSL

Required to access the SolarWinds Information Service API and agent communication

SolarWinds Information Service API

17779 HTTP and HTTPS    

SolarWinds Toolset Integration over HTTP

Agents

The following ports are used by the SolarWinds Orion agent.

Port

Type

Direction

Encryption

Description

22 TCP bidirectional  

Used to install the agent on Linux computers through SSH and SFTP or SCP. Open this port for outbound connections on the Orion server or additional polling engings and inbound connections on the monitored computer.

135 TCP inbound  

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

Active directory, RPC and SMB protocol ports are used by Orion Poller Agent installer to connect to Windows OS and to deploy Windows Agent.

445

TCP

inbound  

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

  • Active directory, RPC and SMB protocol ports are used by Orion Poller Agent installer to connect to Windows OS and to deploy Windows Agent.
17778 TCP bidirectional SSL, TLS 1.0 or later

Send and receive information from Windows and Linux devices polled by agents using agent-initiated communication. Used to deploy agents.

Important: This requirement is for Active agents only. If Passive agents are used, no ports need to be opened on the firewall for the Orion server. For more information, see Changing the Agent Port.

17790 TCP bidirectional SHA1 certificate, TLS 1.0 or later

Used by the agent to communicate with the Orion server when the agent is in server-initiated communication mode.

In Passive mode, port 17790 must be opened on the host where the agent is installed and allowed by the firewall.

17791

TCP

bidirectional  

Used by the agent to communicate with the Orion server when the agent is in agent-initiated communication mode. This port must be opened if the reomte computers you monitor run Windows 2008 R2.

High Availability

The following ports are used in addition to ports used by your primary products when you enable High Availability.

Port

Type

Description

4369

TCP

Open on the main Orion server and its standby server for RabbitMQ clustering. This port exchanges EPMD and Erlang distribution protocol messages for RabbbitMQ. This port is not required when protecting additional polling engines.

5671

TCP

For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers.

25672

TCP

Open on the main Orion server and its standby server for RabbitMQ clustering. This port exchanges EPMD and Erlang distribution protocol messages for RabbbitMQ. This port is not required when protecting additional polling engines.

SAM Component Monitor Ports

Component/
Monitor

Port

Type

Description

DHCP User Experience Monitor

67

UDP

The UDP port used for the DHCP request.

DHCP User Experience Monitor

68

UDP

The UDP port used for the DHCP response.

Directory Size Monitor

 

 

See SAM WMI requirements below.

DNS Monitor
DNS User Experience Monitor

53

TCP/UDP

The TCP and UDP port used for DNS queries.

Download Speed Monitor

19

 

The port used for the character generator service.

File Age Monitor
File Change Monitor
File Existence Monitor
Files Size Monitor

445

TCP/UDP

These components monitor uses TCP/445 and UDP/445 ports.

File Count Monitor

 

 

See "Application Performance Monitor WMI Requirements" on page "4".

FTP Monitor
FTP User Experience Monitor

21

 

This field is the port number used for FTP sessions

HTTP Form Login Monitor
HTTP Monitor
TCP Port Monitor

80

 

This field is the port number used for HTTP forms-based login sessions.

HTTPS Monitor

443

 

The port used by the web site.

IMAP4 Monitor

143

 

 

IMAP4 User Experience Monitor

143 and 993

IMAP4

This component monitor uses these ports when used with a Microsoft Exchange mail server.

IMAP4 User Experience Monitor

25

SMTP

This component monitor uses these ports when used with a Microsoft Exchange mail server.

IMAP4 Port sessions

143

IMAP4

This field is the port number used for IMAP 4 sessions.

IMAP4 Port sessions

585

IMAP4

For Secure IMAP (IMAP4-SSL), use port 585.

IMAP4 Port sessions

993

IMAP4

For IMAP4 over SSL (IMAPS), use port 993.

LDAP User Experience Monitor

389

 

The port used for LDAP connections.

LDAP User Experience Monitor

636

 

For LDAP over SSL, use port 636.

Linux/Unix Script Monitor Ports

22

 

This field allows you to specify the port number used for the SSH connection.

NNTP Monitor

119

UDP

This field is the port number used for NNTP connections.

ODBC User Experience Monitor

1630

TCP

This component monitor uses port TCP/1630.

Oracle User Experience Monitor

1521

TCP

The Oracle SQL*Net Listener allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.

Oracle User Experience Monitor

1526

TCP

The Oracle SQL*Net Listener allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.

Performance Counter Monitor

See description

TCP

This monitor uses RPC, requiring the following ports:

  • TCP/135
  • RPC/named pipes (NP) TCP 139
  • RPC/NP TCP 445
  • RPC/NP UDP 137
  • RPC/NP UDP 138

POP3 Monitor
POP3 User Experience Monitor

110 (default)

 

This field is the port number used for POP3 connections.

POP3 Monitor
POP3 User Experience Monitor

995

 

For Secure POP3 (SSL-POP) use port 995.

POP3 User Experience Monitor
SMTP Monitor

25

SMTP

This component  uses port 25 for SMTP sessions.

SMTP Monitor

465

SSMTP

For Secure SMTP (SSMTP), use port 465.

POP3 Monitor

See Description

 

This component monitor uses the following ports when used with a Microsoft Exchange mail server.

  • 102   X.400 MTA
  • 110   POP3
  • 119   NNTP
  • 143   IMAP4
  • 389   LDAP
  • 563   POP3 over SSL
  • 636   LDAP over SSL
  • 993   IMAP4 over SSL
  • 995   Secure POP3 over SSL

POP3 User Experience Monitor

110 (default)

 

This field is the port number used for POP3 sessions. The default value is 110. For Secure POP3 (SSL-POP) use port 995. It also uses an SMTP Port, port 25 for SMTP sessions.

Process Monitor

 

SNMP

This component monitor uses SNMP communication.

Process Monitor WMI

 

 

Uses WMI communication to test if the specified Windows process is running and uses RPC communication to test if the specified Windows process is running.

RADIUS User Experience Monitor

1812
1645

 

This field is the RADIUS protocol authentication port. The default value is 1812. Cisco devices may require port 1645. This field is the RADIUS protocol accounting port. The default value is 1813. Cisco devices may require port 1646.

RWHOIS Port Monitor

4321

 

This template tests the ability of an RWHOIS server to accept incoming sessions on port 4321.

SQL Server User Experience Monitor

1433

 

This component monitor only works if Microsoft SQL Server is using the default port 1433. If you have a Microsoft SQL Server database that uses a non-standard port, you cannot monitor it using the SQL Server User Experience monitor. You need to use the ODBC User Experience monitor instead to manually define a connection string that will allow you to talk to Microsoft SQL Server on its custom port.

TACACS+User Experience Monitor

49

 

This field is the TACACS+ protocol connection port. The default value is 49.

Tomcat Server Monitor

8080

 

This field allows you to specify the port number used by the web site. The default value for this field is 8080.

VMware Performance Counter Monitor

443

 

Port number to use for VMware API. The default is 443.

ESX Hardware Monitoring

5989

 

Ensure port 5989 is open on the firewall.

Windows Event Log Monitor

 

 

This component monitor uses the following ports:

  • TCP/135
  •  RPC/named pipes (NP) TCP 139
  •  RPC/NP TCP 445
  •  RPC/NP UDP 137
  •  RPC/NP UDP 138
  •  POP3 User Experience Monitor port 110

SAM Templates

Template port requirements will vary depending on how you utilize them. The following provides a list of monitor templates that use ports. 

Template

Port

Description

Blackberry Delivery Confirmation template

25

Blackberry Delivery Confirmation template uses port 25 on the SMTP server for sending the test email. If the SMTP server uses a different port, change this value.

Finger Port Monitor

79

This template tests the ability of the Finger service to accept incoming sessions on port 79.

Gopher Port Monitor

70

This template tests the ability of a Gopher server to accept incoming sessions on port 70.

IRC Port Monitor

6667

This template tests the ability of an IRC server to accept incoming sessions on port 6667.

Java Application Server (SNMP) template

1161

This template is configured to send SNMP requests on port 1161.

SNPP Port Monitor

444

This template tests the ability of an SNPP server to accept incoming sessions on port 444.

Windows FTP Server (via WMI)

21

 This template monitors the Windows FTP Publishing Service and tests the ability of the FTP server to accept incoming sessions on port 21.

SAM WMI Requirements

Microsoft Windows by default uses a random port between 1024 and 65535 for WMI communications. You must create firewall exceptions to allow TCP/UDP traffic on ports 1024 - 65535 or the component monitors and templates that use WMI will not work.

The following component monitors use WMI:

  • Performance Counter Monitor
  • Process Monitor – WMI (if script uses WMI access)
  • Windows Event Log Monitor
  • Windows PowerShell Monitor (if script uses WMI access)
  • Windows Script Monitor
  • Windows Service Monitor (if script uses WMI access)

The following templates use WMI:

  • Active Directory
  • Blackberry Enterprise Server
  • Citrix XenApp 5.0 Core WMI Counters
  • Citrix XenApp 5.0 ICA Session WMI Counters
  • Citrix XenApp 5.0 Presentation Server WMI Counters
  • Citrix XenApp 5.0 Services
  • Errors in Application Event Log
  • Exchange 2007
  • Exchange 2007 Client Access Role Services
  • Exchange 2007 Client Access Role WMI Counters
  • Exchange 2007 Common WMI Counters
  • Exchange 2007 Edge Transport Role Services
  • Exchange 2007 Hub Transport Role Services
  • Exchange 2007 Hub Transport Role WMI Counters
  • Exchange 2007 Mailbox Role Services
  • Exchange 2007 Mailbox Role WMI Counters
  • Exchange 2007 Unified Messaging Role Services
  • Exchange 2007 WMI Counters
  • Exchange 2010 Client Access Role Services
  • Exchange 2010 Common Performance Counters
  • Exchange 2010 Edge Transport Role Services
  • Exchange 2010 Hub Transport Role Services
  • Exchange 2010 Mailbox Role Services
  • Exchange 2010 Unified Messaging Role Services
  • Exchange Server 2000 and 2003
  • Internet Information Services
  • Orion Server
  • SharePoint Server (MOSS) 2007
  • SharePoint Services (WSS) 3.0
  • SQL Server 2005 Database
  • SQL Server 2008 Database
  • Windows Print Services
  • Windows Server 2003-2008

Storage Manager (STM)

Port

Type

Description

22

TCP

Used on the control system for EMC Celerra Storage Devices.

80

TCP

Used on the NetApp head/cluster node and any available CIFS/NFS.

161

UDP

Used for polling of Fiber Channel Switches: Cisco MDS, Brocade, McData, and QLogic Switches.

Used on the EqualLogic Group IP.

162

UDP

Agents use this port to notify Storage Manager Server when information is available to be retrieved from the agent.

If port 162 is in use by Orion NPM, then Storage Manager will use 10162 or 20162 when SNMP traps are sent to the Storage Manager Server.

443

TCP

Storage Manager uses this port to communicate with VMware Virtual Center or ESX server.

Used on the NetApp head/cluster node and any available CIFS/NFS.

1094

TCP

Used by MS SQL application module.

1433

TCP

Used by MS SQL application module.

1521

TCP

Used by Oracle application module.

2463

TCP

Used to set RPC sessions to the storage controller from the SMI-S provider for LSI and SUN StorageTek storage devices.

3306

TCP

Used by the Storage Manager Database.

4319

TCP

Handles the collection from Storage Manager Agents and also acts as a local data collector/agent. Storage Manager communicates with data collectors/agents.

5988

TCP

HTTP port used by SMI-S providers.

5989

TCP

HTTPS port used by SMI-S providers.

8443

TCP

HTTPS port used to communicate with the Storage Profiler Module

9000

TCP

Storage Manager Web Console

17778

TCP

Required for access to the SWIS API

43501

TCP

Java Management Extensions (JMX) if blocked can also use 43052, 43503, and 43504. Allows web server to obtain memory from STM services (collector,

event receiver, maintenance, and poller).

Storage Resource Monitor (SRM)

The following table shows the ports used by SRM:

Port Type requirmentsDescription

25

TCP

SSL/TLS for email alert actions should be enabled.

80

TCP

Default web port. If you specify any port other than 80, you must include that port in the URL used to access the 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. Open the port to enable communication from your computers to the Orion Web Console.

Used on the NetApp head/cluster node and any available CIFS/NFS.

Used by EMC VNX/Clariion for file side performance.

161

UDP

Used for polling storage arrays through SNMP.

Used on the EqualLogic Group IP.

443

TCP

(HTTPS) Used on the NetApp head/cluster node and any available CIFS/NFS.

Used by EMC VNX/Clariion for file side performance.

1433

TCP

Used for communication between the SRM and the SQL Server.

1434

UDP

Used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations.

1801

TCP

MSMQ WCF binding (for more information see this KB:http://support.microsoft.com/kb/183293).

5988

TCP

(HTTP) Used by SMI-S providers.

5989

TCP

(HTTPS) Used by SMI-S providers.

8088

TCP

(HTTP) Backup port used for NetApp DFM management servers for 7-mode arrays.

8443

TCP

(HTTPS) Used by Storage Profiler SWIS.

8488

TCP

(HTTPS) Used for NetApp DFM management servers for 7-mode arrays.

17777

TCP

Orion module traffic. Open the port to enable communication from your poller to the SRM Web Console, and from the SRM Web Console to your poller.

The port used for communication between the Orion Web Console and the poller.

17778

TCP

(HTTPS) Required for access to the SWIS API.

17779

TCP

(HTTP/HTTPS) SolarWinds Toolset integration.

The following condensed table shows the ports used by SRM for collecting data from the storage arrays:

Port Type Storage Array Description
80 HTTP

NetApp ONTAP API,

NetApp DFM clustered mode

Alternate ONTAP API port for NetApp connections.

Alternate connection to NetApp On command for clustered mode management server.

80 HTTP EMC VNX XML API

Alternate connection to the EMC VNX control station for collecting file side performance data.

161 UDP SNMP SNMP connections to the storage array.
443 HTTPS

NetApp ONTAP API,

NetApp DFM clustered mode

Secure ONTAP API port for NetApp connections.

Secure connection to NetApp On command for clustered mode management server.

443 HTTPS EMC VNX XML API

Secure, preferred connection to the EMC VNX control station for collecting file side performance data.

5988 HTTP SMI-S provider Alternate port on SMI-S provider (external or on onboard).
5989 HTTPS SMI-S provider Secure and preferred SMI-S port on SMI-S provider (external or on onboard).
8088 HTTP NetApp DFM 7 mode

Alternate connection to the NetApp On command management servers for 7 mode arrays.

8488 HTTPS NetApp DFM 7 mode

Secure connection to the NetApp On command management servers for 7 mode arrays.

User Device Tracker (UDT)

Port

Type

Description

80

TCP

Used to access the website

161

UDP

Used for SNMP (polling) traffic

1433

TCP

Used to communicate with MS SQL

17777

TCP

Information Service Protocol

Virtualization Manager (VMAN)

Review the following port requirements for the VMAN appliance, the Orion server, Federated Collectors, virtual environments, and additional systems. These ports are required for data collection and management actions.

Features and components affecting the port requirements of the Virtualization Manager appliance include:

  • VMware data collection
  • Hyper-V data collection
  • Active Directory and LDAP authentication
  • Sending email notifications (in alerting and reporting)
  • Sending SNMP traps (in alerting)
  • Orion integration
  • Federated collectors

Port requirements of the master appliance

Port Protocol Service/
Process
Direction Description
22 TCP SSH

Inbound

SSH access to the virtual appliance

25 TCP   Outbound Sends emails through SMTP
123 UDP NTP Outbound Uses the Network Time Protocol (NTP) service
162 UDP   Outbound Sends SNMP traps
389 TCP, UDP   Outbound Active Directory authentication
443 HTTPS   Inbound HTTPS access to the VMAN user interface
443 or 80 TCP   Inbound Performs auto-upgrade or version upgrade on federated collectors if federated collectors are configured
3268 TCP   Outbound LDAP authentication and requests
5480 HTTPS   Inbound HTTPS access to the Management Console
8983     Inbound Access from federated collectors to the master appliance during initial setup
17777 TCP SolarWinds Information Service Bidirectional The port used for communication from your polling engine to the Orion Web Console, and from the Orion Web Console to your polling engine.
17778 HTTPS and TCP SSL Outbound

Communicates with the SolarWinds Orion server and SolarWinds Information Service if the integration with Orion is enabled

If you use Virtualization Manager integrated with NPM or SAM in an environment with multiple polling engines and federated collectors, open TCP port 17778 from the primary collector to every polling engine that is used to poll virtualization data.

61616 TCP   Inbound Active MQ master-collector communication

Port requirements of the federated collector

Port Protocol Service/
Process
Direction Description
22 TCP SSH

Inbound

SSH access to the federated collector

443 or 80 TCP   Outbound Performing auto-upgrade or version upgrade
5480 HTTPS   Inbound HTTPS access to the federated collector
8983       Access from federated collectors to the master appliance during initial setup

Port requirements for data collection

Configure the following outbound ports on the master or the collector for data collection.

Port Protocol Service/
Process
Direction Description
7    

Outbound

Access to Hyper-V hosts that were added by using a fully qualified domain name

135 TCP   Outbound WMI data collection from Hyper-V hosts or VMs
443 TCP   Outbound Data collection from ESX hosts and vCenters
Dynamic RCP ports     Outbound WMI communication. You can configure the available ports on the WMI target or policy.

VoIP & Network Quality Manager (VNQM)

Port #

Protocol Service / process Direction Description
21 TCP SolarWinds Collector Service Bidirectional The port used for FTP (CDR/CMR download)
22 TCP SolarWinds Collector Service Bidirectional

The port used for SFTP (CDR/CMR download) and for

SSH for CLI (operation polling)

23

TCP SolarWinds Collector Service Bidirectional The port used for TELNET for CLI (operation polling)

80

TCP World Wide Web Publishing Service Bidirectional HTTP port

The port used by Additional Web Servers. If you change this setting, you must include the port in the URL used to access the Orion Web Console.

161 UDP SolarWinds Collector Service Outbound The default UDP port of NPM, used by SNMP.
443 TCP World Wide Web Publishing Service Bidirectional The port used for conducting secure SSL communications.
5005 UDP SolarWinds Collector Service Bidirectional

The port used for RTCP data (call metrics) listening from Avaya Call Manager.

5022 TCP SolarWinds Collector Service Bidirectional The port used for communication with Avaya Call Manager via CLI through SSH.
8443 HTTPS SolarWinds Orion Module Engine/Business Layer Plugin Outbound The port used for Cisco Call Manager AXL credentials troubleshooting.
17777 TCP SolarWinds Information Service Bidirectional

The port used for communication from your polling engine to the Orion Web Console, and from the Orion Web Console to your polling engine.

50000 TCP SolarWinds Collector Service Bidirectional The port used for CDR data (call records) listening from Avaya Call Manager.

Web Help Desk (WHD)

The following table provides a list of all of the ports needed for communication with SolarWinds Web Help Desk.

Port

Type

Description

25

TCP

Traffic from the SolarWinds Web Help Desk server to the email server for automated email notifications

80

TCP

HTTP communications with Microsoft Exchange Web Services (EWS)

110

TCP

Non Secure traffic with the POP3 mail server

135

TCP

Asset Discovery using Windows Management Instrumentation (WMI).

WMI calls uses port 135, and then selects a random port for further communication.

143

TCP

Non-secure traffic with the Internet Message Access Protocol (IMAP) mail server

389

TCP

Non-secure traffic from the Web Help Desk server to a designated server (usually a domain controller) for use with the Directory Service tool (LDAP, Active Directory)

443

TCP

Secure traffic with EWS

636

TCP

Secure traffic from the SolarWinds Web Help Desk server to a designated server (usually a domain controller) for use with the Directory Service tool (LDAP, AD)

993

TCP

Secure traffic with the IMAP mail server

995

TCP

Secure traffic with the POP3 mail server

1433

TCP

Communications with a Microsoft SQL external database, including:

  • Microsoft SQL Server
  • Microsoft Systems Management Server
  • Microsoft System Center Configuration Manager (SCCM)
  • SolarWinds Network Configuration Manager (NCM)
  • SolarWinds Network Performance Monitor (NCM)
  • SolarWinds Server and Application Monitor (SAM)

1521

TCP

Communicates with the Oracle Java Database Connectivity (JDBC) connector for asset discovery

3306

TCP

Communicates with the MySQL external database, LANrev, and Casper 8 and lower

4445

TCP

Remote log server reader

5432

TCP

Communications with an External PostgreSQL database

5433

TCP

Communications with Apple Remote 3.2 for asset discovery

7100

TCP

Communications with a Sybase database for asset discovery

8081

TCP

Non-secure traffic from the Web Help Desk Administrator Console

8443

TCP

(Default) Secure traffic from the SolarWinds Web Help Desk Console

17778

TCP

Communications from the SolarWinds Orion server (Orion integration only)

20293

TCP

Communications with an embedded PostgreSQL database

61616

TCP

Web Help Desk Discovery engine (JMS queue port)

Web Performance Monitor (WPM, formerly SEUM)

The following list of ports is required for the WPM Player, Recorder and the Web Interface.

Port

Type

Description

80
(or 8787)

TCP

Default web port. If you specify any port other than 80, you must include that port in the URL used to access the 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 . Open the port to enable communication from your computers to the Orion Web Console. depends on what the default port for the Orion web interface is.

443

TCP

Used when a certificate for encryption to the Orion web interface is installed (SSL/HTTPS)

1433

 TCP

Used for communication between the SolarWinds server and the SQL Server. Open the port from your Orion Web Console to the SQL Server.

17777

 TCP

 Used for Orion WPM traffic.

17781

 TCP

 The default port the SEUM Player listens on. This port must be open between the Orion server and the WPM player for proper communications.

17782

 TCP

Used for player-initiated communications mode

Last modified
13:24, 27 Jun 2017

Tags

Classifications

Public