This article applies to the following ScreenBeam products:
Windows 10, starting from build 1703, supports Miracast on existing wireless network or LAN. ScreenBeam 1100, 1000, and 960 receivers support this feature when enabled through the receiver’s configuration.
How it works (referencing https://docs.microsoft.com)
Users attempt to connect to a Miracast receiver as they did previously. When the list of Miracast receivers is populated, Windows 10 will identify that the receiver can support a connection over the LAN. When the user selects a ScreenBeam receiver, Windows 10 will attempt to resolve the device's hostname via standard DNS, as well as via multicast DNS (mDNS). 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 (P2P) connection.
PIN on connection is supported in Windows 10 build 1809 (and later). If PIN is enabled it will be required on each connection, PIN on first connection only is not supported using Miracast over Infrastructure.