Network Issues

Most network failures fall into discovery, firewall, or node-name consistency problems.

Verify nodes are on reachable network interfaces, on the same subnet (or with multicast routing between subnets).
Check multicast handling (239.2.2.2:3012).
Confirm firewall allows WATCHOUT services and required UDP ports.
Confirm the WATCHOUT process manager is running on the node.
Ensure each node has a unique name. Two live nodes sharing a name route a device to whichever node answers first, so a display can render on the wrong node (a shared name is only for replacing an offline node — see cold spares).
Use the Nodes window Refresh to re-scan, or Wake Up to power on a known but offline node.

Device shows no node, or a warning — the node with that name is offline or not discovered. Confirm it is powered on, networked, and visible in the Nodes window.
Display renders on the wrong node — a name collision: two nodes unintentionally share a name. Rename one to give it a unique name.
Audio device produces no output — the wrong device type or interface, or the device is not enabled. Check the device type and that the device is turned on (see Audio Devices). For driver-specific problems, see Audio Issues.
NDI source not appearing — discovery has not found the stream. See Capture Issues → NDI Capture.
Devices disconnect intermittently — network instability or a firewall block. Check cables, switch health, and firewall rules.

Confirm Director and runners use consistent time strategy.
Check NTP reachability and drift. WATCHOUT resyncs automatically when the NTP offset gets too high.
Resolve time sync warnings before running synchronized playback.

Symptom	Likely cause	Resolution
Dialog says "No ST 2110 interfaces found"	Drivers missing, board not seated, or Runner service not running	Verify the board in the node's hardware list. Reinstall Deltacast drivers. Restart the Runner service.
Output appears configured but no receiver sees packets	Wrong multicast address, wrong VLAN, IGMP snooping off, or sender's PTP did not lock	Verify multicast and port on both ends. Confirm IGMP snooping on the switch. Confirm the sender's PTP is locked.
Receiver shows intermittent black frames or tearing	Single-network packet loss on a busy switch	Turn on ST 2022-7 SPS at both ends. Move ST 2110 traffic onto its own VLAN.
Capture colors look wrong	Color space in the SDP does not match the sender's actual output	Re-export the SDP from the sender. Paste the new SDP into the capture.
PTP never locks	Wrong domain, no PTP leader reachable, or domain conflict on the network	Verify the domain matches the PTP leader. Confirm the PTP leader is on the same VLAN as the ST 2110 port.
Save succeeds but settings do not take effect	The "Restart services" prompt was cancelled	Restart the node's services from the Nodes window, or reopen the dialog and click Apply again.

See Setting Up ST 2110 for the commissioning steps.