Reason Code 49 The RADIUS request did not match with FortiSwitch 248D

joaomanoelc 171 Reputation points

I have a RADIUS with WinServer 2016 and I will use the RADIUS Client FortiSwitch 248D for 802.1X network authentication

when configuring the FortiSwitch as RADIUS Client a log is generated in the NPS with access denied.

Network Policy Server denied access to a user.

Contact the Network Policy Server administrator for more information.

Security ID: NULL SID
Account Name: radius1
Account Domain: -
Fully Qualified Account Name: -

Client Machine:
Security ID: NULL SID
Account Name: -
Fully Qualified Account Name: -
Called Station Identifier:
Calling Station Identifier: -

NAS IPv4 Address:
NAS IPv6 Address: -
NAS Identifier: Fortinet
NAS Port-Type: Ethernet
NAS Port: -

RADIUS Client:
Client Friendly Name: Fortinet
Client IP Address:

Authentication Details:
Connection Request Policy Name: -
Network Policy Name: -
Authentication Provider: -
Authentication Server:
Authentication Type: -
EAP Type: -
Account Session Identifier: -
Logging Results: Accounting information was written to the local log file.
Reason Code: 49
Reason: The RADIUS request did not match any configured connection request policy (CRP).


Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
11,724 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Sunny Qi 10,941 Reputation points Microsoft Vendor


    Thanks for posting in Q&A platform.

    May I know when did you encounter this error? When configured the FortiSwitch 248D as a RADIUS client? If you have configured the FortiSwitch 248D as a RADIUS client in the following option first?


    Please kindly understand that FortiSwitch 248D is a third party product that we're not familiar with, I would suggest you could contact FortiSwitch support for further troubleshooting.

    Best Regards,


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. joaomanoelc 171 Reputation points

    the switch was added as a RADIUS Client as seen in the image.

    the same procedure was done for a WiFi TP-link and it worked without problems.

    when configuring FortiSwitch with the IP and secret password of the RADIUS Server, the validation is done successfully, but immediately afterwards, if you do another test to validate the configuration, it is returned as invalid.


    0 comments No comments