Bit of a crazy issue when deploying a new Ruckus wireless network – in first suspecting an issue with the controller software or perhaps some kind of access control list blocking traffic it turns out that the default Windows Firewall rule for allowing NPS traffic is broken in some fashion.

Having tried this (and it working fine) on Windows Server 2012 R2/2016 it really does appear to be isolated to Server 2019.

Discovering this came about with a few traffic captures combined with the wonderful NTRadPing tool. The fix is to manually create the rule, see the screenshots below on how to do this.

VN:F [1.9.22_1171]
Thumbs up if this article helped you 🙂
Rating: +17 (from 17 votes)
Server 2019 Network Policy Server (NPS) doesn't reply to RADIUS requests, 100% based on 17 ratings

2 Responses to Server 2019 Network Policy Server (NPS) doesn’t reply to RADIUS requests

Leave a Reply

Your email address will not be published. Required fields are marked *