We recently deployed a Windows NPS server using PEAP with MS-CHAP v2 and are allowing only 1 specific AD security group to access a SSID based on user membership in said group. We utilize a Cisco 5508 wireless controller to push the SSID out to all AP's.
The 802.1x SSID is working - mostly. Intermittently users on Windows 10 machines will have issues connecting to the network.
Looking at Event Viewer on the NPS shows Audit Failure's with machine name being passed over instead of the user name. If you continue to just try to connect repeatedly it will eventually try the username and then let's the user connect.
I'm also having an issue where sometimes trying to connect to the 802.1x network will not prompt for credentials. The user will click on the SSID, click Connect, and then Windows shows "Checking network requirements...". It will show this message for 20-30 seconds and then return "Can't connect to this network". Looking at the NPS server Event Viewer will show no authentication attempts for that machine or that user. If I disable the wireless adapter and then immediately re-enable it - it fixes the issue and the user can connect. However, disconnecting from the wireless network or rebooting the machine sometimes causes the issue to return.
Android phones, iPad's, and our Macbooks are not exhibiting this same issue.
Looking at Event Viewer on the NPS shows Audit Failure's with machine name being passed over instead of the user name. If you continue to just try to connect repeatedly it will eventually try the username and then let's the user connect.
I'm also having an issue where sometimes trying to connect to the 802.1x network will not prompt for credentials. The user will click on the SSID, click Connect, and then Windows shows "Checking network requirements...". It will show this message for 20-30 seconds and then return "Can't connect to this network". Looking at the NPS server Event Viewer will show no authentication attempts for that machine or that user. If I disable the wireless adapter and then immediately re-enable it - it fixes the issue and the user can connect. However, disconnecting from the wireless network or rebooting the machine sometimes causes the issue to return.
Android phones, iPad's, and our Macbooks are not exhibiting this same issue.