Microsoft Surface Hub 2 SmCamera - Manual (Page 124)

Miracast over infrastructure
Article • 04/14/2023 • Applies to: Surface Hub, Surface Hub 2S
Miracast over Infrastructure offers many benefits:
Windows automatically detects when sending the video stream over this path is
applicable.
Windows will only choose this route if the connection is over Ethernet or a secure
Wi-Fi network.
Users don't have to change how they connect to a Miracast receiver. They use the
same UX as for standard Miracast connections.
No changes to current wireless drivers or PC hardware are required.
It works well with older wireless hardware that isn't optimized for Miracast over
Wi-Fi Direct.
It uses an existing connection, which reduces the time to connect and provides a
stable stream.
Users attempt to connect to a Miracast receiver through their Wi-Fi adapter. When the
list of Miracast receivers is populated, Windows identifies that the receiver is capable of
supporting a connection over the infrastructure. When the user selects a Miracast
receiver, Windows attempts to resolve the device's hostname via standard DNS, and via
multicast DNS (mDNS). If the name isn't resolvable via either DNS method, Windows
falls back to establishing the Miracast session using the standard Wi-Fi direct
connection.
If you have a Surface Hub or other Windows 10/11 device, then you automatically have
this new feature. To take advantage of it in your environment, you need to ensure the
following is true within your deployment:
Open TCP port: 7250 .
How it works
 Tip
For more information on the connection negotiation sequence, see Miracast over
Infrastructure Connection Establishment Protocol (MS-MICE)
Enabling Miracast over Infrastructure