Resolving Screen Share issues for SMART Board interactive displays with iQ

Issue	Solutions
Mobile devices and computers can’t find the display.	Review the instructions in Configuring the display's network connection to verify they've all been followed. Sometimes it can take several minutes for new connections to propagate through a larger network. All the specified ports must be opened for the devices. Multicast traffic must be enabled. Even if the network is "wide open" and no ports are blocked, ports that should be open to internal traffic must be opened. If many devices (several hundred) are sharing their screens using Screen Share, system issues with board discovery can result. SMART is working on the issue, with a future release planned. To work around this situation for now, provide the display and the device as much network isolation as possible, perhaps using Multicast groups. See Bridging mDNS Connections, below.
Mobile devices and computers can connect, but the quality is poor or the mobile device or computer disconnects.	Test the display using more than one type of device and screen share method to determine what the problem is. If the Browser app in the iQ experience is able to connect to the Internet, the display's hardware is fine. Use a mobile device to create a Wi-Fi hotspot and connect the display and devices to it. Try sharing a screen with Miracast as well. Miracast is a P2P connection that uses WiFi Direct and can point to a network issue. Screen Share problems are very nearly always the result of network or casting-device related issues. Make sure the device supports sharing its screen:. iPhone 4S or later iPad 2 or later iPod touch (5th generation) or later Google maintains a list of Android devices  Windows devices can support both Miracast and Google.   Older devices are more likely to have issues. See Troubleshooting tips to learn more about finding the issue.

Bridging mDNS connections

Multicast Domain Name Server (mDNS) is a protocol that uses IP multicast with DNS to provide the capabilities of a DNS server for service discovery in a small network that does not have a DNS server. IP packets are sent to every node on the network with the reserved mDNS multicast address of 224.0.0.251.

Bridging mDNS traffic requires an mDNS gateway service. One such program is Bonjour Gateway from Cisco Meraki, and Aerohive is another. There are many to choose from. Consult the vendor of the gateway service you choose to learn how to set up an mDNS gateway service with their software. SMART cannot provide support for such setup tasks.

The following section can help you determine if the mDNS service is set up properly..

Troubleshooting tips

Troubleshooting when a device can't find the display

For iOS devices, use Flame Services Browser. For Android devices, use Bonjour Browser on HE.net to see which services are running on the display.  A properly configured network should show the following services under each display's name:

• _airplay._tcp. (Required for AirPlay) 
• _googlecast._tcp. (Required for GoogleCast) 
• _raop._tcp. (Required for AirTunes audio)
• _display._tcp. (Required for Miracast over infrastructure. Only appears when Screen Share is open on the display.)

A device can't connect to the display, performance is choppy or a device can't stay connected to the display

If a device can't connect to the display, some ports are blocked. See Configuring the display's network connection.

If Screen Share's performance is choppy or a device can't stay connected to the display, use HE.net (iOS and Android devices) or Service Browser (Android) to use Traceroute to see the path and latency for each service. 

• _airplay._tcp. (Required for AirPlay) 
• _googlecast._tcp. (Required for GoogleCast) 
• _raop._tcp. (Required for AirTunes audio)
• _display._tcp. (Required for Miracast over infrastructure. Only appears when Screen Share is open on the display.)