Tridium - Ports and there associated protocols for the EC-BOS / JACE - Secured (SSL) & Non-Secured Listing

 

Port

Used For

 

25

SMTP email.  Without this port open the JACE cannot send email alarm messages.

TCP

37

Timesync feature uses this.  Without this the JACE cannot use the internet to sync the time.

TCP

80

The JACE's Non-Secure, and default port for HTTP / Web User Interface Access.  This can be changed rather easily to match the port provided by the customer.  Note this in the JACE info spreadsheet if changed.

TCP

443

The JACE's Secured (SSL) Web HTTPs port for Web User Interface Access.  This can be changed rather easily to match the port provided by the customer.  Note this in the JACE info spreadsheet if changed.

TCP

1911

For Non-Secured FOX communications protocol.  This port needs to be available so that we can run Workbench (the Jace Engineering Tool) and access platform level programming.  Access to this port will help reduce service costs as we often times will not have to dispatch a technician to service the system.

TCP

4911

For Secured FOXs (SSL) communications protocol.  This port needs to be available so that we can run Workbench (the Jace Engineering Tool) and access platform level programming.  Access to this port will help reduce service costs as we often times will not have to dispatch a technician to service the system.

TCP

3011

This is default for the Platform Daemon, which can also be opened to allow for remote service. Non-Secure

TCP

5011

This is for the Secure (SSL) Platform Daemon, which can also be opened to allow for remote service.

TCP

1930

Distech Plugins LON

TCP

1931

Distech Plugins BACnet

TCP

47808

BACnet Network Service

UDP

Add Feedback