Edge HMI

List of network ports used by this software

Save PDF

List of network ports used by this software

Save PDF

Last UpdatedOct 29, 2026
3 minute read

This is a list of the various network ports that are used by the project runtime, its subordinate drivers and utilities, and other related programs.

Port	Feature or Protocol
20	FTP Server (Data)
21	FTP Server (Command)
80	Web Server (HTTP), unencrypted
102	Siemens SIMATIC S7 Protocol, for the SIETH and SITIA drivers
110	Post Office Protocol version 3 (POP3), for incoming mail
118	Microsoft SQL Server Services
135	Distributed Component Object Model (DCOM), for OPC DA and OPC HDA
161	Simple Network Management Protocol (SNMP)
162	Simple Network Management Protocol (SNMP) Trap
389	Lightweight Directory Access Protocol (LDAP), unencrypted
443	Web Server (HTTPS), encrypted using SSL
465	Simple Mail Transfer Protocol (SMTP), for encrypted outgoing mail
502	Modbus TCP/IP, for the ADPRO, MODSL, MOTCP, and SCHNE drivers
587	Simple Mail Transfer Protocol (SMTP), for encrypted or unencrypted outgoing mail
636	Lightweight Directory Access Protocol (LDAP), encrypted using SSL
1028	FTP Client (Command)
1029	FTP Client (Data)
1234	AVEVA Edge project runtime server (also known as Data Server or TCP/IP Server), unencrypted Tip: You can change this port number in your project settings. For more information, see Communication tab.
1433	Microsoft SQL Server
1434	Microsoft SQL Server Dedicated Administrator Connection (DAC)
1521	Oracle
1526	Oracle
2030	Oracle
3000	Python Language Server port (WebSocket) - will try 3000, 3002, 3004, 3006
3306	MySQL (can be configured to use 3306–3309)
3872	Oracle Management Remote Agent
3997	Studio Database Gateway (StADOSvr.exe) Tip: You can change this port number in the gateway settings, especially if you need to run multiple instances of the gateway. For more information, see Manually running Studio Database Gateway.Traffic on this port is protected only when Secure Channel is enabled.
4322	Remote Agent (CEServer.exe), RemoteAgent without Use TLS enabled
4323	RemoteAgent with Use TLS enabled
4448	Mobile Access Runtime (MobileAccessTask.exe)
5432	PostgreSQL
22350	Wibu CodeMeter, for the License Server feature
32565	AVEVA Historian (connection from Studio Database Gateway to the Historian server; the port can be changed in the Historian Configurator)
44818	Allen-Bradley CIP (default), for the ABCIP driver
47808	BACNet UDP (default), for the BACNE driver
48010	OPC UA Server (default) Tip: You can change this port number in your project settings. For more information, see Configure the communication settings for OPC UA Server.
51234	AVEVA Edge project runtime server (such as Data Server or TCP/IP Server), encrypted via TLS/SSL Tip: You can change this port number in your project settings. For more information, see Communication tab.

Notes

Depending on which features you use in your project, you might need to update your network's firewall settings in order to open the corresponding ports and allow the traffic to pass through. For example, if you develop your project to send email alerts, you need to open port 25 for SMTP.

Many of the port numbers listed above are only the defaults for those ports. You can change them, but if you do, you need to do so on both the server side and the client side, and then you also need to update the firewall settings. Keep in mind that the project runtime acts as the server in some cases and as the client in others, depending on the feature or protocol.

The communication drivers (for example, MOTCP, ABCIP, BACNE) included in the list above are only a few of the most commonly used drivers. For more information about the port used by a specific driver, see the documentation for that driver.

Studio Database Gateway sends an ICMP echo request (ping) to the AVEVA Historian server before it connects. If the ping is blocked, the connection fails. Allow ICMP echo from the gateway computer to the Historian server, together with the Historian port.

Edge HMI