Wireless Display
PreviousNetwork RequirementsNextI am unable to see Miracast (AirServer) as a destination to mirror to
Last updated
Last updated
Below you can find a table of ports being used by AirServer on Mago Room
AirServer.exe process (located in C:\Program Files\ValareaPOD\Air_Server\ ) on Mago Room uses the following Bonjour services:
_airplay._tcp
_googlecast._tcp
_display._tcp
_airserver._tcp
_raop._tcp
Note: The Miracast adapter broadcasts a message announcing that is is available for a connection on one of the three non-overlapping 2.4 GHz 802.11 channels 1, 6 and 11. The pairing negotiation between the computer/device and the Miracast receiver always initiates over 2.4 GHz no matter if your computer/device is connected to the router using a 2.4 GHz and/or 5 GHz channel and/or there is no WiFi network at all.
Miracast screen mirroring requires Windows Display Driver Model (WDDM) 1.3 or newer.
To check the WDDM version, please follow the steps below:
Press Windows Key + R, enter "dxdiag" and press ENTER.
Let the tool (DirectX Diagnostic Tool) collect all information
Press “Save All Information...”.
Save and open the resulting text file and search for WDDM.
Miracast screen mirroring also requires a Miracast-compatible graphics adapter/card and a Wi-Fi adapter/card with, at least, NDIS 6.3 drivers on both the receiving and transmitting device. If you are unsure about this, you can check whether or not your computer running Mago Room airserver process supports Miracast by following these steps:
Open up a Command Prompt window
Write "netsh wlan show driver" and press ENTER
The command prompt will show you whether or not your device is Miracast compatible
If the command prompt displays the "The Wireless AutoConfig Service (wlansvc) is not running."-error, you can try to enable to. In order to fix this, you can follow these steps:
Press Windows Key + R and enter “services.msc” followed by the ENTER key
Find “WLAN AutoConfig” in the list of service, right-click it and select Properties
Press Start & change the startup type as "Automatic"
Restart your computer
C:\Windows\System32\WUDFHost.exe Allow In/Out connections for TCP and UDP, Ports: All
Application: All applications Action: Allow network traffic Direction: Inbound Protocol: TCP/UDP Port(s): Specific ports: 5353, 7236,7250
Check and disable AP-isolation on access point in order to allow client-to-client communication
Computer Configuration - Windows Settings - Security Settings - Wireless Network (IEEE 802.11) Policies. There should be a setting for wireless policies. Double click the setting for wireless policies. Tab Network Permissions:
● Check "Allow" everyone to create all user profiles
● Uncheck "Don't Allow" WiFi Direct groups Note: Your Windows security policies must not prevent Miracast pairing nor creation of the Microsoft Wi-Fi Direct Virtual Adapter nor a new DIRECT-XXXXXXX-XXXXX network. You must allow in your policies, to create a new virtual peer-to-peer connection all the way.
Go to: Settings - System - Projecting to this PC - Windows PCs and Phones can project to this PC ... - and change to: "Always Off". If you need PIN request before to project, select Require PIN for pairing>ALWAYS
When you try to connect you should see a new DIRECT-XXXXXXX-XXXXX network and a new Microsoft Wi-Fi Direct Virtual Adapter being created in Network Connections during the pairing. If not, it will be your security policies preventing this. If they are created but pairing is not successful, they both should vanish after some time. But this would indicate some other problem and not security settings.
► Make sure that all drivers especially chipset, graphics and WiFi network adapter ones are up to date.
This support article was last updated on Mon, 1 Feb, 2021 at 4:27 PM.
