Likely causes, most useful checks first
- Client and panel are on different networks or isolated VLANs.
- Casting service or receiver is not active.
- Network policy blocks discovery or required traffic.
- Client application or panel software is out of date.
Safe checks
Record the exact failure point
Note whether the panel is not discovered, a code is rejected, or connection starts and drops.
What the result means: This distinction prevents unrelated resets and gives IT a useful symptom.
Confirm network context
Check that the client and panel are connected to the intended network and that guest isolation is not separating them.
What the result means: If networks differ, ask the network administrator for the approved casting route.
Restart only the casting endpoints
Close and reopen the casting app, then restart the panel's casting receiver using normal menus.
What the result means: Retest before changing network or factory settings.
Test a second client
Try another approved device on the same network.
What the result means: One failing client suggests a client-side issue; all clients failing suggests panel service or network policy.
Sources
Reviewed under the BoardFaults safe-external-check policy · risk class: low · updated 2026-09-03