This article applies to the following ScreenBeam products:
Click on the to expand selection.
When attempting to connect to a ScreenBeam with a Windows 10 device there are a few things to check if your connection is unsuccessful:
If you are unable to see the ScreenBeam in your connection menu it may be your wireless card.
If you are unable to see the ScreenBeam in your connection menu it may be your wireless card. By default, ScreenBeams use a 5GHz channel for wireless display, so you must have a dual-band wireless card. You can check the model of your wireless card in Device Manager on your PC, look in the Network Adapters section. If you don’t have a dual-band wireless card check out these workarounds.
If you can see the ScreenBeam in the Connect menu, but the connection fails
If you can see the ScreenBeam in the Connect menu, but the connection fails, the first thing we recommend is to disconnect from any VPN software and try to connect to the receiver again. VPN software may block your connection, click here for more information.
If you can see the receiver in the Connect Menu, and can enter the PIN, but the connection immediately fails after PIN entry
If you can see the receiver in the Connect Menu, and can enter the PIN, but the connection fails after PIN entry this can be caused by Group Policy.
If you’re using a managed device you will need to check your Group Policies, this article should help you out
Once you’ve ruled out VPN and Group Policy, make sure you have the latest drivers for your Graphics and Network cards.
Once you’ve ruled out VPN and Group Policy, make sure you have the latest drivers for your Graphics and Network cards. Out of date drivers can stop a connection or cause intermittent connection issues. You can check your driver versions by going to Device Manager and expanding Network Adaptors section, copy the name of your wireless card and Google the name of your card and look for driver updates from your PC OEM or the hardware OEM. The process is the same for your Graphics card. Windows Update does not always have the latest drivers, which is why we recommend this process.
Firewall settings may also need to be adjusted antivirus software is a consideration also
If you’re able to get connected to ScreenBeam, but experience dropped connections or performance issues check out these suggestions.
When connected to the ScreenBeam you see black bars surrounding the image on all sides of the screen
When connected to the ScreenBeam if you see black bars surrounding the image on all sides of the screen.
This is most likely due to an Intel Graphics setting you will need to set the Screen Size to 100% in the Intel Graphic Properties wireless section you can find instructions here
If after connecting to the receiver your display screen is black you need to check your display settings
If after connecting to the receiver your display screen is black you need to check your display settings, you must select either duplicate or extend. While in extended mode you will only see your Windows background and not your icons and shortcuts.
No sound output
You can think of ScreenBeam as a wireless HDMI connection. Once connected the audio playback device is automatically changed to the ScreenBeam and the attached display. If your display does not have speakers the sound will seem to be muted, to correct this left click your volume control and be sure to select your PC speakers.
While playing video, if the audio is out of sync or the video is stuttering and choppy
While playing video, if the audio is out of sync or the video is stuttering and choppy your laptop may not meet the minimum hardware requirements or have enough available resources for smooth playback. Check our tips on resource management
Another issue that can cause choppy video is poor wireless signal between the ScreenBeam and your laptop, or between your laptop and your internet connection, for mitigation strategies use this article
If your Windows Desktop Freezes or Locks Up When I Try to Connect to ScreenBeam
There is an issue that may occur on Windows systems where components of the desktop may freeze or lockup when connecting to ScreenBeam. This behavior typically occurs when a user reconnects to ScreenBeam, either by the side or top overlay panels, immediately after a failed connection. This results in the overlay panels being frozen on the screen and various desktop components, such as the system tray, becoming unresponsive. The PC will typically need to be rebooted to recover from this state. Click here for information and link to the Hotfix.
When deploying your ScreenBeams you must take several variables into account.
When deploying your ScreenBeams you must take several variables into account. Our recommended best practice is to stagger P2P channels on receivers that are adjacent to each other, as well as avoiding the channels that your infrastructure APs are on, this reduces the possibility for interference. Depending on the size of your room and density of wireless devices you will want to adjust the transmit power, it is recommended to use medium or high. You can read more tips in our Miracast Whitepaper here