Issue
Sigma fails to communicate properly when installed on a PC where the Windows Firewall is enabled. This affects both Sigma Server and Sigma Client installations, resulting in loss of communication with controllers or other Sigma components.
Product Line
Satchwell BAS & Sigma
Environment
- Sigma Server
- Sigma Client
Cause
Sigma requires specific TCP and UDP ports to be open for communication. On systems where the firewall is enabled (especially on corporate networks), these ports may be blocked by default. This prevents Sigma components from exchanging data, leading to communication failures.
Resolution
Step 1: Allow Sigma Through the Firewall Prompt (Client Only)
- On first launch of SigmaClient, Windows may prompt to allow the application through the firewall.
- Click “Allow access” when prompted.
Step 2: Manually Create Firewall Rules (All Systems)
Perform the following steps on both the Sigma Server and all Sigma Client PCs:
-
Open Windows Firewall with Advanced Security:
- Go to Control Panel > Windows Defender Firewall > Advanced Settings
- Or search for “Windows Defender Firewall with Advanced Security” in the Start menu
-
Create Inbound Rules:
- Click Inbound Rules > New Rule
- Select Port, then click Next
- Choose UDP, enter port:
49152, click Next - Select Allow the connection, click Next
- Choose applicable profiles (Domain, Private, Public), click Next
- Name the rule (e.g.,
Sigma UDP 49152), click Finish
-
Repeat the process for the following TCP ports:
- TCP 8080 (used for Sigma web services or diagnostics)
- TCP 3614 (used for Sigma communication)
-
(Optional) If using custom ports, repeat the steps above with those port numbers.
Step 3: Verify Communication
- Restart the Sigma Server and Clients.
- Confirm that communication with controllers and other Sigma components is restored.
