Skip to content

Troubleshooting

Access and connectivity

Web interface is unreachable

Symptom: Browser cannot connect to http://172.16.112.1.

Possible cause Fix
Wrong Ethernet port used Ensure you are connected to port 3 (LAN, left side), not port 7 (LAN DATA).
Computer IP address not on the same subnet Set your computer's interface to a static IP in the 172.16.112.x range, e.g. 172.16.112.2 / 255.255.255.0. See Installation.
Device IP was changed to an unknown address Perform a factory reset — the device will return to 172.16.112.1.
DHCP was enabled and device received a different address Check your DHCP server's lease table for the device's MAC address.
Device is not powered on Check the power adapter and indicator lights.

Cannot find the device after enabling DHCP

  1. Check your router or DHCP server's connected-device list for the TS Analyzer's MAC address (shown in Settings → Network before you enabled DHCP, or on the label on the device).
  2. On Windows, run arp -a in Command Prompt.
  3. On Linux/macOS, run arp -n.

If nothing works, reset the device to restore static IP 172.16.112.1.

Forgot the login password

The web interface has no password recovery option. Perform a factory reset, which restores the default password admin along with the default network settings.

Signal monitoring

No transport stream detected on IP input

Possible cause Fix
Stream is not being sent to the correct address/port Verify source address and multicast group match the input configuration.
Firewall blocking UDP Check firewall rules on the network path between the source and the analyzer's LAN DATA port.
Multicast TTL too low Check the TTL value on the source — a value of 1 limits the stream to a single LAN segment.
Wrong port used IP streams must be connected to port 7 (LAN DATA, 1 Gb/s), not the management port.

RF signal present but no stream decoded

Possible cause Fix
Incorrect frequency or modulation configured Verify the RF input configuration matches the broadcast parameters (frequency, standard, symbol rate).
Signal level too low or too high Check Level, SNR, and BER readings on the RF monitoring panel. See RF Signal Monitoring.
Antenna not connected Verify the RF cable and connector at port 4.

Error counters increasing unexpectedly

Start with CCE (Continuity Count Error) — it is both the most common and the most diagnostic error in MPEG TS monitoring. Check which PIDs are affected to determine the scope (whole stream vs. individual service). See Level 1 Errors and Error Contexts for a structured approach.

Time and NTP

UTC deviation shown in monitoring view is large

  • Confirm that NTP synchronization is enabled and the device has network access to NTP servers.
  • Verify the correct timezone is set in Settings → System Time → Change Timezone.
  • If NTP servers are blocked on your network, configure a local NTP server address in the NTP server list.

Support

If you cannot resolve an issue, contact Stream Labs technical support:

Have the device serial number ready — it is shown in Settings → Device Info.