Skip to content
  • There are no suggestions because the search field is empty.

ScreenBeam BrowserCast connection error code reference

This article applies to the BrowserCast feature on ScreenBeam 1100 Plus, FLEX and 1000EduG2.

When utilizing BrowserCast for screen sharing, users might see an error message dialog stating:

If you have not already done so, consult the deployment guide to ensure your network firewall and ports are configured for BrowserCast support.

Error code
What it means
Possible causes
Recommended tips
BC-ERROR-01

Your browser couldn’t start WebRTC because it didn’t get any network candidates.

 
  • Browser blocked by firewall or security software

  • Corporate network restrictions

  • VPN interference

  • Browser WebRTC permissions blocked

  • Try disconnecting from VPN

  • Switch to another Wi-Fi or hotspot

  • Restart the browser or try a different one

  • Check if your network blocks WebRTC

 BC-ERROR-02

The ScreenBeam receiver couldn’t collect network candidates for WebRTC.

 
  • Receiver blocked by firewall or network policies

  • Corporate or campus network restrictions

  • WAN isolation / multicast restrictions

  • Device-level WebRTC blocking

  • Move receiver to a less restrictive network

  • Test using a mobile hotspot

  • Verify the receiver can reach the internet

  • Check firewall rules for STUN (UDP 3478)

BC-ERROR-03

Both sides are blocked from starting WebRTC.

 

 
  • Very strict corporate firewall

  • VPN security policies

  • STUN/UDP completely blocked

  • Network outage

  • Test both devices on a hotspot

  • Check if the organization blocks WebRTC traffic

  • Ensure both devices have internet access

  • Temporarily disable VPN or security software

BC-ERROR-04

Both sides got STUN  (Session Traversal Utilities for NAT) candidates, but their NAT types do not allow a direct connection.

 

 
  • Both sides behind symmetric NAT

  • Strict port/firewall rules

  • Deep packet inspection blocking UDP

  • Try connecting both devices to the same network

  • Move to a more open network (home, hotspot)

  • Disable or switch VPN

  • Ask IT to allow outbound UDP 3478

BC-ERROR-05

The receiver is unable to obtain a public-facing network candidate.

 
  • Receiver behind strict enterprise firewall

  • Symmetric NAT

  • ISP or carrier-grade NAT restrictions

  • Try putting the receiver on the same network as the browser

  • Use a hotspot for testing

  • Ask IT to allow outbound UDP 3478

  • Avoid guest networks with isolation enabled

BC-ERROR-06

Your browser could not obtain a public-facing ICE candidate.

 

 
  • Browser behind corporate firewall

  • VPN blocking STUN

  • Router security settings

  • Antivirus/endpoint protection

  • Try another network or hotspot

  • Disconnect VPN

  • Check browser privacy extensions blocking WebRTC

  • Use the same network as the receiver

BC-ERROR-07

Both the browser and receiver are blocked from STUN, so WebRTC cannot traverse NAT.

 
  • Strict enterprise networks on both ends

  • STUN blocked

  • Symmetric NATs on both sides

  • Try connecting both on the same network

  • Test with a hotspot

  • Avoid guest/VLAN-isolated networks

  • Ask IT to allow WebRTC traffic (UDP 3478)

BC-ERROR-08

A fallback case for unexpected or rare ICE (Interactive Connectivity Establishment) failures.

  • Temporary network instability

  • Router bugs

  • Race conditions/timing issues

  • Misconfigured proxies

  • Retry the connection

  • Switch networks or use a hotspot

  • Refresh browser

  • Reboot the receiver