Setting up for success with screen sharing

When deploying a screen sharing solution, the most important factor is reliability, which often goes hand in hand with ease of use. After all, if something doesn’t work regularly, it makes it difficult to use, which in turn makes people less likely to keep using it. To make sure your deployment of SMART's screen sharing technology goes smoothly and creates a reliable experience, consider these important questions:

  • 1. When should each protocol be used?

    Protocol

    Devices

    Ideal for

    Considerations

    AirPlay

    Apple devices

    Organizations that primarily use Apple devices for sharing to a display.

    The display must support AirPlay. AirPlay works natively only with Apple devices.

    AirPlay may not be the right choice for complex or restricted networks. AirPlay requires Bonjour and multicast traffic to be allowed on networks. Many organizations disable this traffic to keep networks secure and efficient. Bonjour repeatedly scans for compatible devices, increasing the traffic on a network, and doesn’t easily work across multiple subnets.

    AirPlay is limited when there are separate networks, such as a when employees use one network while guests or students use another. Screen sharing with AirPlay won’t work when displays and client devices are on different networks.

    Google Cast

    Google devices

    Android and Chrome operating systems

    Chrome browser

    Some Google apps

    Organizations that primarily use Android or Chrome devices or a browser for sharing to a display.

    The display and client device or app must support Google Cast.

    Google Cast may not be the right choice in complex or restricted networks. Google Cast requires multicast (mDNS) traffic to be allowed on networks. Many organizations disable this traffic to keep networks secure and efficient. mDNS repeatedly scans for compatible devices, increasing the traffic on a network, and it doesn’t easily work across multiple subnets.

    Miracast

    Windows computers

    Some Android devices

    Organizations that primarily use Miracast-enabled devices, such as Windows computers.

    The display and client must support Miracast.

    Miracast devices can share using a peer-to-peer connection (also known as P2P or Wi-Fi Direct): it establishes Wi-Fi connections directly between devices without using an intermediate access point.

    P2P might sound beneficial for freeing up bandwidth on existing networks, but it can be susceptible to signal interference. It is also limited to the security measures set by the device’s manufacturer. P2P may not be compatible with the organization’s network security policies.

    SMART Mirror or SMART Screen Share client app

    Apple devices

    Google/Chrome OS devices

    Chrome browser

    Windows devices

    Android devices

    Organizations that require technology that supports a wide range of device types.

    Organizations that need more robust screen sharing features.

    Pros of using a solution like SMART Mirror or SMART Screen Share:

    • Compatibility with numerous device types

    • Works with complex networks

    • Consistent user experience, making training and adoption easier

    • Organizations don’t have to make additional changes to their network to support native protocols if they're only using the client app.

    • Additional screen sharing features. Learn more.

    Notes 

    • App download is required.

    • No app download is required if using the SMART Mirror web client app.

  • 2. Is the network infrastructure set up for screen sharing?

    The network's infrastructure plays an important role in screen sharing's quality, speed, reliability, and stability. Therefore, it's important to ensure that the network is set up properly to support this type of activity. To achieve this, the network infrastructure must have a high-speed and reliable connection, such as a wired or high-speed wireless network. The network must also be able to handle high levels of traffic without becoming too congested, as this can lead to dropped frames, delays, and poor image quality.

    In addition, the infrastructure must be secure to prevent unauthorized access to the network and to protect the data being transmitted during screen sharing.

    Consulting a network engineer can help ensure the network infrastructure is properly set up for screen sharing and the rest of your organization's network activity.

  • 3. Is the network architecture set up to minimize packet loss and jitter?

    To minimize packet loss and jitter, it is important to design and configure the network to support the types of traffic that will be transmitted over the network. Although SMART recommends you consult a network engineer to help optimize the network, here are some ways in which the network’s architecture can affect packet loss and jitter:

    • Network topology: The topology of a network refers to how its components are connected to each other. In a network with a centralized topology, all traffic passes through a central hub, which can increase the chances of packet loss and jitter if the hub becomes congested. On the other hand, in a distributed network, traffic is distributed across multiple paths, which can reduce the chances of congestion and improve the overall performance. When using a distributed network, transitions will need to be fast.

    • Network Congestion: Network congestion occurs when there is more traffic than the network can handle. Congestion can cause packets to be dropped or delayed, leading to packet loss and jitter. Network architecture can affect congestion by determining the number of devices on the network, the available bandwidth, and the routing protocols used to manage traffic.

    • Quality of Service (QoS): QoS is a set of technologies that allow network administrators to prioritize certain types of traffic over others. By prioritizing real-time traffic, such as video and voice, over non-real-time traffic, such as email and web browsing, QoS can reduce the chances of packet loss and jitter.

  • 4. If the organization is using subnets, is the proper traffic routing in place?

    Subnets, referred to as VLANs in certain cases, are often used in corporate and school networks to keep device traffic separate from other device traffic. For example, subnets can keep discovery traffic such as mDNS, Bonjour, and multicast announcements from flooding to other networks. This traffic policing can prevent devices from discovering each other, such as displays with SMART Mirror on a corporate network, and devices on a guest Wi-Fi. To use screen sharing in a network with subnets, you need to allow bidirectional IP routing between the subnets that support screen sharing and user devices.

  • 5. Are the correct ports opened on the network for the screen sharing protocols your organization is using?

    Many devices have native, built-in screen sharing protocols that allow data to be wirelessly transmitted from one place to another. Common screen sharing protocols include:

    • AirPlay

    • Google Cast

    SMART’s screen sharing apps also include their own set of protocols. To support all of these protocols, there are a number of ports that need to be opened. If they are not opened, screen sharing will not work and devices won’t be able to connect to a display and broadcast.

    SeeConfiguring the network for screen sharing

  • 6. Does the network casting resolution bandwidth meet the requirements?

    The video transmission between the broadcasting and sharing device requires a certain amount of bandwidth to deliver a smooth video playback. The frame rate is one of the key factors that affect the bandwidth requirement. The video should be at least 20 fps (frames per second), because anything less than 20 fps can result in choppy and disjointed video playback, which can be frustrating and difficult to watch.

    This table lists the bandwidth required for 20 fps for a variety of video resolutions:

    Source video resolutionRecommended bandwidth

    4K

    20 Mbps

    HD 1080p

    5 Mbps

    HD 720p

    2.5 Mbps

    SD 480p

    1.1 Mbps

    SD 360p

    0.7 Mbps

  • 7. Does the network’s latency meet the requirements?

    Latency can cause a noticeable delay between what you do on the broadcasting device and what appears on the display. This is particularly important for tasks that require real-time feedback, such as sharing a screen, where even a small delay can make the experience seem to lag and appear unresponsive. A latency of less than 100 ms is important for screen sharing because it helps ensure a smooth and responsive user experience.

  • 8. Has the required network traffic been allowed?

    For screen sharing to work, the network and firewall must be properly configured to allow the required traffic. This includes ensuring the correct ports are open and that the network’s allowlist is updated.

  • 9. Have you secured screen sharing from unwanted traffic?

    To help you prevent unwanted traffic from being shared to a display, the screen sharing app on SMART Board interactive displays has some security features you can enable.

    Turn on Moderator mode to control who presents. When this setting is enabled, people who have connected devices must be invited to share their screen from the display. This helps prevent people from taking over screen sharing before you want them to.

    You can enable permissions to receive a prompt on the display to allow device connection.