If so, check the NPS event log for other references to that user account. Check to see if the events are associated with a single user account. The reason code indicates the cause of the failure. Check the reason codes of the authentication failure events.

Contact the Network Policy Server administrator for more information. However, when we try to connect through the NPS server with a radius client we receive no response and in the NPS server where the MFA Extension is installed the following event is generated: Network Policy Server discarded the request for a user.I have a RADIUS with WinServer 2016 and I will use the RADIUS Client FortiSwitch 248D for 802.1X … Reason: The connection request did not match any configured network policy.Reason Code 49 The RADIUS request did not match with FortiSwitch 248D. Logging Results: Accounting information was written to the local log file. EAP Type: Microsoft: Secured password (EAP-MSCHAP v2) Account Session Identifier:. I have popped in my test laptop into wireless devices and my username who is a domain admins into wireless users. I have created 2 AD groups one called wireless devices and wireless users. Can anyone advice me on what I am doing wrong. Reason Code: 49 Reason: The RADIUS request did not match any configured connection request policy (CRP).Came across an odd problem at work the other day involving NPS and Wireless APs. when configuring the FortiSwitch as RADIUS Client a log is generated in the NPS with access denied. I have a RADIUS with WinServer 2016 and I will use the RADIUS Client FortiSwitch 248D for 802.1X network authentication. Reason Code 49 The RADIUS request did not match with FortiSwitch 248D.

Radius extension dll