---
title: "Network Architecture"
slug: "network-architecture"
updated: 2026-03-04T15:23:15Z
published: 2026-03-04T15:23:15Z
canonical: "documentation.lakesidesoftware.com/network-architecture"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Architecture

Communication between the SysTrack master server and endpoint systems occurs via web sockets and is encrypted using SSL/TLS. The communication uses port 443 and the HTTPS protocol.

- Agents on endpoint systems do not need any special ports open to communicate with the SysTrack master.
- If there is more than one master system, TCP ports 57632 and 57633 must be open between masters.
- SysTrack Deploy communicates with the master system using TCP port 57632.
- Inter-process communication takes place on the master system using TCP port 57633.
- If Microsoft 365 integration with SysTrack is enabled, access to the following Microsoft internet services is required:
  - [https://graph.microsoft.com](https://graph.microsoft.com/)
  - [https://login.microsoftonline.com](https://login.microsoftonline.com/)

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/endpoint_system.png)

## Network Traffic

- Default port for agent communication: 443
- Average network usage per device: ~2.3 MB per day
- If databases are sent back to the master (caching), this will add an average of approximately 30mb per system, a minimum of once a day. This can also occur each time a system goes offline (logout/shutdown).

## Authentication Options

- NTLM
- Kerberos (may require port 88 for KOC communications)
- Negotiate (uses NTLM/Kerberos)
- S-Channel (all machines need certificates)
- Anonymous (none)