Port requirements for PI Data Archive
- Last UpdatedOct 03, 2024
- 1 minute read
- PI System
- PI Server 2018
- PI Server
|
Functionality |
Remote application |
Protocol |
Port |
Direction1 |
Local application |
Service |
|---|---|---|---|---|---|---|
|
Establish client connections to Data Archive |
All client applications |
TCP |
5450 |
Inbound |
Data Archive |
PI Network Manager |
|
Authentication - SPN registration (PI mappings) |
Domain Controller |
TCP/UDP |
135 |
Outbound |
Data Archive |
PI Network Manager |
|
Authentication - Kerberos (PI mappings) |
Key Distribution Center |
TCP/UDP |
88 |
Outbound |
PI client |
PI Network Manager |
|
Authentication - NTLM (PI mappings) |
Domain Controller |
TCP/UDP |
Dynamic |
Outbound |
Data Archive |
PI Network Manager |
|
IP/Host lookup (PI Trust) |
DNS |
UDP |
53 |
Outbound |
Data Archive |
PI Network Manager |
|
Domain/OSUser lookup (PI Trust) |
Domain Controller |
TCP/UDP |
Dynamic |
Outbound |
Data Archive |
PI Network Manager |
1 Direction is in relation to the computer where is running. For example, Outbound means that firewall rules for the node must allow traffic to leave the and be directed towards the remote node; Inbound means that firewall rules for the node must accept incoming connections from the remote node.
For more details about port requirements, see the Knowledge Base article: Which firewall ports should be opened for the PI Server / PI Data Archive?