Skip to content

Revise steps for customizing event service port #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kdejoyce wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

Revise steps for customizing event service port #85

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
87b0743
Revise steps for customizing event service port
kdejoyce Jan 29, 2026
045ec0d
Change product references to be accurate
kdejoyce Jan 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions ...iguration-and-administration/how-to-customize-event-service-listening-port-s.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,14 @@
---
description: 'Shows how to change Event Service listening ports for Netwrix Threat Prevention using pgAdmin by editing the defend_config table and restarting the service.'
description: 'Shows how to change Event Service listening ports for Netwrix Threat Manager using pgAdmin by editing the defend_config table and restarting the service.'
keywords:
- Event Service
- listening port
- pgAdmin
- defend_config
- Netwrix Threat Prevention
- Threat Manager
- Threat Prevention
- Netwrix Threat Prevention
- Netwrix Threat Manager
- port configuration
- FS port
- AD port
Expand All @@ -22,13 +24,13 @@ knowledge_article_id: kA04u00000110h7CAA
You need to customize Threat Manager listening ports for the Event Service due to customer or environmental requirements.

## Cause
Customer or environmental requirements dictate that the default Netwrix Threat Prevention Event Service listening port(s) must be changed.
Customer or environmental requirements dictate that the default Netwrix Threat Manager Event Service listening port(s) must be changed.

## Resolution
Alter the default Netwrix Threat Prevention Event Service listening port(s) via PGAdmin:
Alter the default Netwrix Threat Manager Event Service listening port(s) via PGAdmin:

1. Install the latest PGAdmin Console: https://www.pgadmin.org/download/
2. Connect to the Netwrix Threat Prevention database. You will have to create a “Master” password for PGAdmin as well as enter the Netwrix Threat Prevention database password: `DEFEND124!!`
2. Reach out to Netwrix support to gain access to the Netwrix Threat Manager database.
3. Select **Tables** > **defend_config table**
4. Right click and select **View/Edit Data** > **First 100 Rows**
5. Change the Value for the port in question on line 2 (`10000` is the Default FS Port and `10001` is the Default AD Port):
Expand All @@ -41,4 +43,4 @@ For example, change the FS port to `514` and click **OK**:
![port512.png](../0-images/ka0Qk000000DkZh_0EM4u000008LC2a.png)

6. In the window below click the **Save Data Changes** icon.
7. Restart the Netwrix Threat Prevention Event Service.
7. Restart the Netwrix Threat Manager Event Service.