Network Considerations

The following should be taken into consideration in regards to network settings and communications

• If a local proxy is configured (in the Internet Explorer Options dialog), the option Bypass proxy server for local addresses must be checked, or some features depending on local communication will not work.

Firewall/Port considerations

The following describes all of the ports that can be used by an OL Connect solution. IT staff may decide the firewall strategy to follow for their internal requirements and needs depending on the statements outlined herein.

	Listens on port #	Destination port #	Type	Comment
Messenger	5863/5864	5863/5864	TCP+UDP	Used for inter-module communication
Connect Server	9340		TCP	Used for Connect REST API
Connect Server	9350		TCP	Dedicated internal connection for inter-process communication (i.e. between engines)
HTTP Server	8080		TCP
HTTPS Server	443		TCP
NodeJS Server	9090		TCP
NodeJS HTTPS Server	8443		TCP
SMTP Input plugin	25, or 587 when encryption is enabled		TCP
Email Input plugin		110	TCP	Default POP3 port
Secure Email Input plugin		993	TCP
Send Email plugin		25	TCP	Default SMTP port
Secure Email Output plugin		587	TCP
LPR		515	TCP
LPD	515		TCP
Telnet	9100		TCP
FTP Input/Output		21	TCP
MySQL	3306		TCP+UDP
Microsoft SQL Server	1433		TCP+UDP
HyperSQL	9001		TCP

• Port numbers in bold type are user configurable.
• Port numbers in bold underlined type are based on the type of database used.
• Some of the ports listed above may also be used by other modules.
• User-configurable modules may use other ports entirely, depending on the settings defined by the end user. A few examples:
  The Create Email Content plugin will use the port defined in the Mail host setting in Workflow (see OL Connect Preferences).
  The ports used by the HTTP Client Input task, Legacy SOAP Client and SOAP Client plugin depend on the configured URL.