Best Practices for Deploying ScreenBeam Miracast Over LAN
This article is applicable to ScreenBeam 1xxx-Series and 960 products.
Executive Summary
Wireless display is foundational for collaboration across enterprises and schools. While classic Miracast uses Wi-Fi Direct (peer-to-peer), Miracast over LAN routes discovery-initiated sessions over your existing wired/wireless network. When paired with ScreenBeam receivers, this approach scales better, is simpler to manage, and fits enterprise security models.
Scope note: Miracast over Infrastructure is only available on Windows 10/11 devices.
How Miracast Over LAN Works (and Why It Helps)
Windows discovers ScreenBeam receivers using Wi-Fi Direct radio beacons. After discovery and hand-off, the media and control traffic traverse the LAN/WLAN.
Placement tip: Because discovery is RF-based, place receivers in proximity to user devices (same room is recommended).
Key benefits
-
Scalability: Concurrent sessions without consuming scarce Wi-Fi Direct spectrum.
-
Centralized management: ScreenBeam CMS + existing network tooling.
-
Security: Enterprise VLANs, authentication, and access controls.
ScreenBeam fit
ScreenBeam receivers support wired/wireless LAN operation and provide centralized configuration, monitoring, and updates.
Deployment Best Practices
1) Network Readiness & Capacity
-
Confirm LAN/WLAN bandwidth for the expected concurrency.
-
Use Gigabit Ethernet uplinks to minimize latency/jitter.
-
Validate switching/routing handles multicast reliably (used for discovery workflows and supporting services).
- Assure the following firewall ports are allowed
Function Receiver Port Client Port Protocol Direction Protocol 7250 Any TCP Bidirectional MDNS Discovery 5353 5353 UPD Bidirectional DNS
53 53 TCP/UDP Bidirectional HDCP
25030 Any TCP Bidirectional RTSP Any 7236 TCP Bidirectional RTP 24030 Any UDP To ScreenBeam HW Cursor 19134 Any UDP To ScreenBeam UIBC Touchback Any 50000 TCP To Client
2) ScreenBeam Configuration
-
Update firmware to the latest release before pilot/rollout.
-
Enable Miracast over LAN in the receiver settings.
-
Assign DHCP reservations or static IPs for receivers; standardize naming (site-room-display).
3) WLAN Optimization (for wireless clients)
-
Prefer 5 GHz access for clients; survey spectrum and avoid congested channels.
-
Ensure WMM/QoS is enabled so real-time traffic isn’t deprioritized.
-
Do not disable Wi-Fi on Windows clients—Wi-Fi Direct is required for discovery even when streaming over LAN.
4) Multicast & Discovery
-
Enable IGMP Snooping on access/aggregation switches.
-
If senders/receivers span VLANs, configure multicast routing on L3 devices.
-
Validate discovery and session setup under realistic load.
5) Security Controls
-
Segment with VLANs; restrict admin interfaces to trusted networks.
-
Enforce WPA2/WPA3 on WLANs.
-
Gate access with ACLs, NAC, or MAC allowlists per policy.
6) Physical & Environmental
-
Prefer wired Ethernet to receivers where feasible.
-
Place receivers in-room, within typical Wi-Fi Direct range, minimizing obstacles.
-
Use cable management to prevent accidental disconnects.
Pre-Deployment Checklist
-
Capacity validated; Gigabit uplinks confirmed
-
Wi-Fi Direct discovery tested in-room; receivers placed near users
-
IGMP Snooping enabled; multicast routing (if multi-VLAN) verified
- DHCP reservations/static IPs; clear device naming
-
5 GHz plan + WMM/QoS confirmed; spectrum surveyed
-
VLAN/ACL/NAC rules verified; admin access restricted
-
CMS monitoring configured; update/change cadence defined