Why am I still getting a PIN request when connecting even though I configured it for "First Connection" only?
The PIN behavior is not matching what I have configured on the ScreenBeam settings.
Not all the PIN settings apply to each display protocol. See descriptions below to help understand how each display protocol handles PIN requests.
- Miracast P2P: All the PIN settings apply. PIN on each connection or on first connection only apply.
- Miracast over LAN: There is no "PIN on first connection only". It's either PIN is disabled, or PIN is on. When 'On' it ignores the first connection or each time setting. This is per Microsoft's design. If PIN is enabled it will always ask for a PIN.
- Airplay: For Airplay, PIN requests differentiate between macOS and iOS.
- macOS: PIN is generally asked for on each connection. Regardless of whether "first connection" or "each connection" is selected, of if Static or Random PIN is selected - it will always ask for a PIN. The only exception is if the user disconnects the session and immediately reconnects within a few seconds.
- iOS: PIN is not dependent on the "first connection" or "each connection" setting, but rather if Static or Random PIN generation is selected. If Static, PIN will be prompted only on initial connection and is persistent after that. If Random, then PIN is requested on each connection.
- macOS: PIN is generally asked for on each connection. Regardless of whether "first connection" or "each connection" is selected, of if Static or Random PIN is selected - it will always ask for a PIN. The only exception is if the user disconnects the session and immediately reconnects within a few seconds.
- Google Cast: This protocol does not support PIN pairing
- BrowserCast: Has its own separate PIN settings. PIN must always be entered to identify the receiver to connect to. PIN settings are limited to how often the PIN code refreshes value. PIN will always change to a new value per session.