SiteManager Embedded (SM-E) Requirements for Internet access
This article provides information on SiteManager Embedded's requirements for internet access.
By default, SM-E will automatically try all the different methods and protocols to connect to GateManager.
ACM/PXP (port 11444): This is a dedicated port for connecting to the GateManager server. Using a dedicated port has the advantage that 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. 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)
This connects to GateManager using the TLS protocol on port 443. This should work through firewalls that allow outgoing HTTPS connections.
TLS over HTTP (port 80)
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 outgoing HTTP connections.
Access via Web-proxy
Generally, SM-E will search the Windows registry for information about available web proxies. Such information may originate from a user's configuration of a web browser, or the web browsers automatic detection of the web proxy via the WPAD protocol.
TLS via Web-proxy
This connects through a Web Proxy, requesting that Web Proxy connects to GateManager on port 443. Once established, the normal TLS protocol is used.
HTTP via Web-proxy
This connects through a specified Web Proxy, re-questing that Web Proxy to connect to the GateManager on port 80. Once established, the connection is upgraded to a secure TLS connection.
Via NTLM Web-proxy
This connects through a specified NTLM-based Web Proxy (aka MS NT LAN Manager), requesting that Web Proxy connects to GateManager on port 80 or 443. Once established, the connection is upgraded to a secure TLS connection
More details in the pdf below