Skip to main content

Protocols and Ports Required

To ensure successful data collection and activity monitoring, Auditor has to communicate through firewall and requires some ports to be opened for inbound and outbound connections.

RECOMMENDED: Netwrix recommends reviewing your current port configuration after every re-installation or upgrade.

If you use...Do the following...
Windows FirewallIf you are running Windows Firewall on the computer where Auditor Server is going to be installed, the 135, 9004, 9699, 9011, and one dynamic port will be opened automatically for inbound connections during Auditor installation. For outbound rules, create or enable predefined Windows Firewall rules. Before installing Auditor, make sure that the Windows Firewall service is started.
Third-party FirewallIf you use a third-party firewall, you must create rules manually.

Follow the steps to create Firewall rules manually.

The example below applies to Windows Firewall and explains how to create a rule for inbound connection.

Step 1 – Start the Windows Firewall service.

Step 2 – Navigate to Start > Control Panel and select Windows Firewall.

Step 3 – In the Help Protect your computer with Windows Firewall page, click Advanced settings on the left.

Step 4 – In the Windows Firewall with Advanced Security dialog, select Inbound Rules on the left.

Step 5 – Click New Rule. In the New Inbound Rule wizard, complete the following steps:

  • On the Rule Type step, select Port.
  • On the Protocol and Ports step, select TCP or UDP. In the Specific local ports field specify the port number.
  • On the Action step, select the Allow the connection action.
  • On the Profile step, make sure that the rule applies to all profiles (Domain, Private, Public).
  • On the Name step, specify the rule's name, for example Netwrix Auditor TCP port_number Access.

In most cases, this configuration is enough to ensure successful data collection and processing. If your organization policy requires you to provide a justification for each particular port, review the following for a full list of ports to be opened on the computer where Auditor Server is going to be installed and on your target servers.

Netwrix Auditor Server

During installation, Netwrix Auditor automatically creates inbound Windows Firewall rules for the essential ports required for the product to function properly. If you use a third-party firewall, make sure to allow inbound connections to local ports on the target and outbound connections to remote ports on the source.

Tip for reading the table: For example, on the computer where Netwrix Auditor client is installed (source), allow outbound connections to remote 135 TCP port. On the computer where Netwrix Auditor Server resides (target), allow inbound connections to local 135 TCP port.

PortProtocolSourceTargetPurpose
135TCPComputer where Netwrix Auditor client is installedNetwrix Auditor ServerNetwrix Auditor remote client console
9004TCPMonitored computersNetwrix Auditor ServerNetwork Traffic Compression Services responsible for user activity monitoring
9011TCPComputers where Netwrix Auditor for Windows Server Compression Services resideNetwrix Auditor ServerNetwork traffic compression and interaction with hubs and services
9699TCPScript / query hostNetwrix Auditor ServerNetwrix Auditor Integration API
Dynamic: 1024 -65535TCPComputers where Netwrix Auditor Server and Netwrix Auditor client are installedNetwrix Auditor ServerNetwrix Auditor internal components interaction. Allow C:\Program Files (x86)\Netwrix Auditor\Audit Core\NwCoreSvc.exe to use the port.
For Managed Service Providers: 443TCPNetwrix Auditor ServerNetwrix Partner PortalReporting on active MSP licenses
- 80 for http - 443 for httpsTCPSSRSNetwrix Auditor ServerReports If your environment is configured differently, we recommend that you check with your DBA or the SSRS settings through the Configuration Manage.

In most environments, the rules are created automatically and you do not need to open more ports to ensure successful data collection.

In rare cases, for example if your security policies require you to provide a justification for opening each particular port, you might need a more detailed overview.