SiteManager Connection Method

This article provides information on how a Secomea SiteManager connects to a GateManager, and which TCP Ports are used and which protocols.

By default, a SiteManager will automatically try a series of different methods and protocols to connect to a GateManager Address

(Example: IP: 193.242.155.118 DNS: gm08.secomea.com)

• ACM/PXP (port 11444 TCP): This is a dedicated port for connecting to the GateManager server. Using a dedicated port is normally preferred as it separates GateManager related traffic from other outbound traffic in your network, so you can more easily track GateManager traffic on your local network and on your Internet connection. But using a dedicated port also means that you will probably need to open this port in the company firewall, which may go against corporate policy rules.
• HTTPS/TLS (port 443 TCP): This connects to GateManager using the TLS protocol on port 443. This should work through firewalls that allow outbound HTTPS connections.
• TLS over HTTP (port 80 TCP): This connects to GateManager using the standard HTTP port 80 but immediately upgrades that connection to a secure TLS connection. This may work through a firewall that only allows outbound HTTP connections.
• TLS via Web-proxy: This connects through a specified Web Proxy (see below), requesting that Web Proxy connects to GateManager on port 443 TCP. Once established, the normal TLS protocol is used.
• HTTP via Web-proxy: This connects through a specified Web Proxy (see below), requesting that Web Proxy connects to GateManager on port 80 TCP. Once established, the connection is upgraded to a secure TLS connection.

Additional outbound connections

Additionally, the SiteManager will do lookups to 193.242.155.50-59 port 80 asking if its GateManager address is known. This is a built-in feature of the SiteManager which can be seen as a service for the end-user.

If a customer has his own GateManager. It has public IP xx.xx.xx.xx and the customer needs to change it to xx.xx.yy.yy. Secomea can then create the “NATTING” in the GateManager discovery service saying that SiteManagers connecting to xx.xx.xx.xx should connect to xx.xx.yy.yy