ScreenBeam 1xxx-Series Network Port Requirements
Applies to: ScreenBeam 1000 EDU, 1000 EDU Gen 2, 1100 Plus, and 1100 FLEX. Feature availability varies by model and firmware version.
Overview
ScreenBeam 1xxx-Series receivers support multiple wireless display protocols, including BrowserCast, Miracast, AirPlay, and Google Cast. Each protocol uses specific network ports for device discovery, connection establishment, and audio/video transmission.
The following table outlines the network port requirements to help IT administrators configure firewalls, VLANs, and network security policies.
Important: Only the ports associated with the features and protocols enabled in your environment need to be permitted.
Network Port Requirements
| Connection / Service | Receiver / Local Port | Client / Remote Port | Protocol | Purpose / Direction |
|---|---|---|---|---|
| BrowserCast | ||||
| Signaling | 49152–65535 | 443 (Cloud) |
TCP -HTTPS/WSS |
Outbound to Internet; to https://screenbeam.me |
| TURN | 3478 | 3478 | TCP | |
| STUN / NAT Traversal | 49152–65535 | 19302, 3478, 5349 | UDP | Outbound; conditional* |
| WebRTC Media | 49152–65535 | 49152–65535 | UDP | Bidirectional audio/video |
| Miracast over LAN | ||||
| mDNS Discovery | 5353 | 5353 | UDP | Bidirectional discovery |
| DNS | 53 | 53 | TCP/UDP | Name resolution |
| Connection Setup | 7250 | Any | TCP | Connection establishment |
| HDCP | 25030 | Any | TCP | Content protection |
| RTSP | Any | 7236 | TCP | Session control |
| RTP | 24030 | Any | UDP | Audio/video transmission |
| Hardware Cursor | 19134 | Any | UDP | Cursor data |
| UIBC | Any | 50000 | TCP | Touchback/input to client |
| AirPlay | ||||
| mDNS Discovery | 5353 | 5353 | UDP | Device discovery |
| RTSP / AirPlay | 47000 | Any | TCP | Session control |
| RTSP / BLE | 7000 | Any | TCP | BLE-assisted connection |
| AirPlay Audio | 7100 | Any | TCP/UDP | Audio transmission |
| AirPlay Video | 18000–18009 | Any | TCP/UDP | Video transmission |
| Google Cast | ||||
| mDNS Discovery | 5353 | 5353 | UDP | Device discovery |
| DNS | 53 | 53 | TCP/UDP | Name resolution |
| NTP/SNTP | 123 | 123 | UDP | Time synchronization |
| Cast Communication | 8008 | Any | TCP | Client/receiver communication |
| Cast Communication | 8009 | Any | TCP | Google Cast communication |
| HTTP | 80 | Any | TCP | Web communication |
| HTTPS | 443 | Any | TCP | Secure communication |
| SSDP | 1900 | Any | UDP | Service discovery |
| Media Streaming | 32768–61000 | Any | UDP | Audio/video transmission |
| System Services | ||||
| NTP Time Server | 123 | 123 | UDP | Time synchronization |
Network Considerations
BrowserCast
- Supported on ScreenBeam 1000 EDU Gen 2, 1100 Plus, and 1100 FLEX.
- Requires Internet access for signaling and session establishment.
- UDP is recommended for optimal audio/video performance. TCP fallback may introduce additional latency.
- Supports cross-VLAN connectivity when appropriate routing and firewall rules are configured.
Miracast
- Miracast P2P uses Wi-Fi Direct and typically requires no corporate LAN firewall changes.
- Miracast over LAN uses the existing network and requires appropriate client-to-receiver communication.
AirPlay and Google Cast
- Device discovery may require mDNS forwarding when clients and receivers are on different VLANs.
- Google Cast requires access to applicable Internet services.
Recommended Network Best Practices
- Wired Ethernet: Connect ScreenBeam receivers to wired Gigabit Ethernet whenever possible.
- Client Wi-Fi: Use 5 GHz Wi-Fi with at least 80% signal strength or equivalent.
- Firewall Configuration: Permit the required ports between authorized client and receiver networks.
- VLAN Routing: Ensure appropriate routing and discovery mechanisms are configured across VLANs.
- Network Security: Keep receiver firmware updated and restrict management access to authorized administrators.
Additional Information: ScreenBeam Conference, CMS Enterprise, and other management services may require additional network ports not covered in this article.