Sigma Server Communication to ARCNET/Ethernet Subnets via a DNN Failing

[Product_Support]

Issue

Sigma server is unable to retrieve communication statistics from the DNN or the controllers downstream of the DNN.

Product Line

Satchwell BAS & Sigma

Environment

Satchwell Sigma

Cause

The Sigma server relies on RIP (Routing Information Protocol) messages broadcast by the network DNNs to learn the network topology. This process depends on the RIP Listener service or equivalent routing configuration, which is:

• Disabled by default on Windows XP
• Deprecated or removed in later versions of Windows (Vista through 10)

Resolution

To restore communication between the Sigma server and the ARCNET/Ethernet subnets via the DNN, choose the appropriate method based on the operating system:

---

For Windows XP

Enable RIP Listener:

1. Open Control Panel.
2. Select Add or Remove Programs.
3. Click Add/Remove Windows Components.
4. Highlight Network Services → click Details.
5. Check RIP Listener → click Next and Finish.

   

---

For Windows Vista, 7, 8, 10

Use Persistent Static Routes (Recommended):

Since RIP Listener is no longer supported, configure static routes manually:

1. Open Command Prompt as Administrator.

2. Use the following command to add a persistent route:

   route -p add <destination_network> mask <subnet_mask> <gateway_ip>

   Example:

   route -p add 192.168.100.0 mask 255.255.255.0 192.168.1.1

3. Verify routes using:

   route print

   

4. Refer to the article: Persistent Routing on the Sigma Server for detailed steps.

---

Additional Notes

• RIP v1 is considered insecure and obsolete in modern networks.
• Static routing is more predictable and secure in environments where dynamic routing is not feasible.
• Always validate connectivity after changes using ping, tracert, or route print.