Port requirements
SolarWinds strongly recommends that you install Web Help Desk on a server that is protected from unauthorized access by the public. If your use of Web Help Desk does not need to be public or internet-facing, install it on a server that is neither public, nor internet-facing. To learn about best practices for configuring your Web Help Desk installation securely, see Best practices to secure SolarWinds Products.
Review and open ports for WHD to support communications to and from the WHD server. These secure and non-secure ports are used to access the following WHD resources:
- WHD interfaces
- External and embedded databases
- Email traffic
- LDAP and Active Directory
- Asset Discovery
- Firewall port requirements for data traffic
WHD interfaces
The following table lists the WHD ports for secure and non-secure interface traffic.
| Port | Protocol | Description |
|---|---|---|
| 80 | TCP | HTTP communications with Microsoft Exchange Web Services (EWS) |
| 443 | TCP | Secure traffic from the WHD Administrator Console |
| 8081 | TCP | Non-secure traffic from the WHD Administrator Console (Windows, Linux, macOS) |
| 8443 | TCP | (Default) Secure traffic from the WHD Administrator Console (Windows, Linux, macOS) |
| 61616 | TCP | WHD Discovery engine (JMS queue port) |
External and embedded databases
The following table lists the WHD ports for external and embedded database communications.
| Port | Protocol | Description |
|---|---|---|
| 1433 | TCP |
Communications with a Microsoft SQL external database, including:
|
| 3306 | TCP |
Communications with a MySQL external database (such as Casper 8 and lower) Beginning in WHD 12.7.3, LANrev is no longer supported. |
| 5432 | TCP | Communications with an External PostgreSQL database |
| 17778 | TCP | Communications from the SolarWinds Orion server (Orion integration only) |
| 20293 | TCP | Communications with an embedded PostgreSQL database |
Email traffic
The following table lists the WHD ports for email traffic.
| Port | Protocol | Description |
|---|---|---|
| 25 | TCP | Traffic from the WHD server to the email server for automated email notifications |
| 80 | TCP | Non-secure traffic with Microsoft Exchange Web Services (EWS) |
| 110 | TCP | Non-secure traffic with the POP3 mail server |
| 143 | TCP | Non-secure traffic with the Internet Message Access Protocol (IMAP) mail server |
| 443 | TCP | Secure traffic with EWS |
| 993 | TCP | Secure traffic with the IMAP mail server |
| 995 | TCP | Secure traffic with the POP3 mail server |
LDAP and Active Directory
The following table lists the WHD ports for Lightweight Directory Access Protocol (LDAP) and Microsoft Active Directory.
| Port | Protocol | Description |
|---|---|---|
| 389 | TCP | Non-secure traffic from the WHD server to a designated server (usually a domain controller) for use with the Directory Service tool (LDAP, Active Directory) |
| 636 | TCP | Secure traffic from the WHD to a designated server (usually a domain controller) for use with the Directory Service tool (LDAP, Active Directory) |
Asset Discovery
The following table lists the WHD ports for Asset Recovery.
| Port | Protocol | Description |
|---|---|---|
| 135 | TCP |
Asset Discovery using Windows Management Instrumentation (WMI). For WMI calls, use port 135 and then choose a random port for further communication. |
| 1521 | TCP | Communications with the Oracle Java Database Connectivity (JDBC) connector for asset discovery |
| 3306 | TCP | Communications with the MySQL external database, LANrev, and Casper 8 and lower |
| 4445 | TCP | Remote log server reader |
| 5433 | TCP | Communications with Apple Remote 3.2 for asset discovery |
| 7100 | TCP | Communications with a Sybase database for asset discovery |
Firewall port requirements for data traffic
Firewalls between any two points of communication must have the requisite ports open to inbound or outbound traffic according to the relative direction of the communication traffic.
For additional port information, see: