Part Iii Configuring The Infrastructure Network; Wired Network - ActionTec Screenbeam 960 Deployment Manual

Wireless display over lan
Hide thumbs Also See for Screenbeam 960:
Table of Contents

Advertisement

Part III Configuring the
Infrastructure Network
Wireless display over LAN can allow ScreenBeam to stream video over both wireless and
Ethernet networks. While all devices are normally connected wirelessly, those connecting
over LAN rather than P2P directly to the ScreenBeam receiver rely upon properly-configured
wireless access points and a wired Ethernet connection for enhanced stability and throughput.
Since the stream quality and user experience heavily relies on the network's performance,
consider adjusting your network and Wireless APs for optimal performance as recommended
below.

3.1 Wired Network

A ScreenBeam connection to a wired 1Gbps Ethernet complying with IEEE 802.3ab /
1000BASE-T using shielded Cat5e or better cable is strongly preferred. A 100Mbps IEEE
802.3u / 100BASE-TX compliant connection is the minimum requirement.
Whenever possible, use the following guidelines to assist in successful ScreenBeam receiver
deployment:
Use non-blocking switches/routers to avoid intermittent connection issues over
infrastructure.
Use Quality-of-Service features on switches and routers to prioritize ScreenBeam port
traffic.
Employ policies for managed devices to prevent CPU-intensive or high-bandwidth tasks
such as online backups during times when wireless presentations may occur.
Use virtual LANs (VLANs) with routing to sequester traffic on subnets wherever
possible.
For iOS/macOS native screen mirroring and wireless mirroring over LAN, the multicast
DNS (mDNS) protocol is required on port 5353 UDP. Since this protocol broadcasts the
ScreenBeam receiver's presence to all IP addresses on a subnet, some network switches
may be configured to block traffic on this port to prevent excessive use of network
bandwidth by such traffic. It is important to configure switches to pass mDNS traffic to all
stations on a network so they become visible to user devices. If this cannot be done,
solutions exist that can cache mDNS broadcast requests and send them out of band to all
WAPs in a network without the corresponding bandwidth burden. Consult the
documentation from the WAP manufacturer or network vendor on how to deploy such
solutions.
© 2018 Actiontec Electronics Inc. All rights reserved.
9
ScreenBeam Deployment Guide

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents