Problem Authentication Radius
Dear @Dbarbosasx ,
Thank you for raising questions.
we have a post about how to set up radius server,
If you have further questions, please feel free to contact us.
DearThanks for helping us!We performed the procedure you sent, but it didn't work.The message we get in the Server Windows 2016 event viewer is the same:Reason Code: 49Reason: The RADIUS request did not match any configured connection request policy (CRP).We followed other Zyxel Kbs for Radius configuration and it didn't work either.seu comentário0
@Zyxel_SilviaThanks for helping us!We performed the procedure you sent, but it didn't work.The message we get in the Server Windows 2016 event viewer is the same:Reason Code: 49Reason: The RADIUS request did not match any configured connection request policy (CRP).We followed other Zyxel Kbs for Radius configuration and it didn't work either.seu comentário0
Hi @Dbarbosasx ,
In Windows Server, there are two policy folders under [NPS > Policy]. Based on the log you provided, the issue is relating to the first folder misconfiguration named “Connection Request Policy” (CRP).
Policies in this folder are used to define if the server should user its own database, or proxy the request to the other authentication server. Where we can define the criteria and corresponding action. (Just like your case) If the incoming request doesn’t match any of the criteria, the error log will then occur.
So, we recommend you to use the “NPS Wizard” to create all related rules for Wi-Fi authentication.
First, please follow the directory as the screenshot below, and click “Configure 802.1X”
Next, select “Secure Wireless Connection” in the initial page.
Then, click “add” to put Zyxel AP in the trusted RADIUS Client
Be sure you enter the correct IP address and the Secret (which should be the same as the value set on the Nebula>SSID Setting page)
(make sure the Secret is the same between Nebula and RADIUS Server)
In the next page, allow PEAP
Click the “Configuration”, please make sure the selected certificate allows “server authentication”
In the User Group, specify the User scope you’d like to use for 802.1X
After that, you’ve completed the entire setting. Simply click finish, restart your NPS Server to ensure the settings are applied, and then the server can be used for 802.1X authentication for wireless access!
- 8.4K All Categories
- 1.6K Nebula
- 70 Nebula Ideas
- 56 Nebula Status and Incidents
- 4.5K Security
- 226 Security Ideas
- 980 Switch
- 46 Switch Ideas
- 870 WirelessLAN
- 22 WLAN Ideas
- 5.1K Consumer Product
- 155 Service & License
- 280 News and Release
- 97 Success Stories
- 58 Security Advisories
- 13 Education Center
- 578 FAQ
- 261 Nebula FAQ
- 160 Security FAQ
- 76 Switch FAQ
- 74 WirelessLAN FAQ
- 7 Consumer Product FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 69 About Community
- 46 Security Highlight