Ports Protocols & Ports Forwarding

Ports and Protocols

Resilio Connect uses specific ports and protocols to properly function. Depending on the network your Agents are in, these must be open to let traffic flow between the Agents, Management Console, and the Tracker Server. The Management Console communicates with the Agents using TCP.

Once the Management Console and Agents are communicating, the Resilio Connect Agents must also be able to transfer data to and from other Agents. Agents transfer data to each other using TCP and UDP. To make this possible the necessary ports must be opened and forwarded on all firewalls, NATs, and routers between the Agents.

What Ports are required by Resilio Connect? *

Management Console

Agent

* UDP is optional and if your organization doesn't allow it the Tracker will still work.
** Connect Agents can be configured to transfer data using only TCP or UDP if your organization limits the transmission of one these protocols
*** Multicast is optional and if your organization doesn't allow it there are other ways to enable Connect Agents to transfer data.

Port Forwarding

If your Management Console (and default Tracker Server) are behind a Firewall and you have WAN based Agents, you may need to enable port forwarding from you WAN based IP address to your LAN based computer (hosting the Management Console) for the following:

* Resio Connect Ports can also be customized in your environment
** By default the tracker runs on the same machine as the Management Console, but can be placed on another machine if preferred

Agent Connection to Management Console

For Connect Agents to communicate with the Management Console, they require a configuration file (sync.conf) which contains the IP address (or DNS name), and security credentials of the Management Console. This is so they can:

• Establish a secure connection to the Management Console
• Send file and job operation events
• Connect to other Agents and receive Agent policy