This Article will provide information on the SiteManager Embedded's requirements for internet access.
By default, the SM-E will automatically try all the different methods and proto-cols to connect to the GateManager:
ACM/PXP (port 11444): This is a dedicated port for connecting to the Gate-Manager server. Using a dedicated port has the advantage that it separates the GateManager related traffic from other out-bound traffic in your network, so you can more easily track the 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 collide with corporate policy rules.
HTTPS/TLS (port 443): This connects to the GateManager using the TLS protocol on port 443. This should work through firewalls that allow out-going HTTPS connections.
TLS over HTTP (port 80): This connects to the GateManager using the standard HTTP port 80, but immediately upgrades that connection to a se-cure TLS connection. This may work through a firewall that only allows out-going 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 users 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 to connect to the 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 to connect to the GateManager on port 80 or 443. Once established, the connection is up-graded to a secure TLS connection
More details in the pdf below.