If you have a Surface Hub or other Windows 10 device that has been updated to Windows 10, version 1703, then you automatically have this new feature. If the name is not resolvable via either DNS method, Windows 10 will fall back to establishing the Miracast session using the standard Wi-Fi direct connection.įor more information on the connection negotiation sequence, see Miracast over Infrastructure Connection Establishment Protocol (MS-MICE) Enabling Miracast over Infrastructure When the user selects a Miracast receiver, Windows 10 will attempt to resolve the device's hostname via standard DNS, as well as via multicast DNS (mDNS). When the list of Miracast receivers is populated, Windows 10 will identify that the receiver is capable of supporting a connection over the infrastructure. Users attempt to connect to a Miracast receiver through their Wi-Fi adapter as they did previously. It leverages an existing connection which both reduces the time to connect and provides a very stable stream.It works well with older wireless hardware that is not optimized for Miracast over Wi-Fi Direct.
No changes to current wireless drivers or PC hardware are required.They use the same UX as for standard Miracast connections. Users do not have to change how they connect to a Miracast receiver.Windows will only choose this route if the connection is over Ethernet or a secure Wi-Fi network.Windows automatically detects when sending the video stream over this path is applicable.Miracast over Infrastructure offers a number of benefits: This functionality is based on the Miracast over Infrastructure Connection Establishment Protocol (MS-MICE). This should improve performance in poor network conditions.Beginning with Windows 10 version 1703, Microsoft extended the ability to send a Miracast stream over a local network rather than over a direct wireless link. This will limit AirPlay and Google Cast to 720p30, while Miracast will be limited to 1080p30. Switch on "Limit Mirroring Resolution to reduce bandwidth" in the Display tab of Advanced Settings.Make sure the device you want to mirror to AirServer is within sufficient range of your Wi-Fi.You should preferably also configure your router to only use Wi-Fi-n or Wi-Fi-ac (if supported). Use iStumbler (Mac) or NetStumbler (PC) to see which Wi-Fi channels are in use around you, then configure your router to use a channel that is free.Try connecting your computer to the network with an ethernet cable and check if the performance is better. It is also possible that your connection cannot handle the bandwidth.In most cases, this resolves jitter and lag related issues.
Visit the router manufacturer’s website and download / install the latest firmware. Your router might be running old firmware.Make sure your AirServer Windows 10 Desktop Edition is up-to-date by checking for updates in the Microsoft Store app.Here are a few things you can try to improve this: There can be a number of causes for laggy or choppy connections when using Windows 10 Desktop Editon. This support article was last updated on Tue, 16 Feb, 2021 at 11:24 AM. Windows 10 Desktop Edition When I mirror to AirServer Windows 10 Desktop Edition, the connection is very laggy.