Forum Discussion
NTRadPing gets rejected by Win2016 NPS
jay26cee Try changing your condition from "Access Client IPv4 Address" to "Client IPv4 Address"
Also make sure you enable logging under Accounting and create your log files in a format you can manage. Because you are being rejected by NPS, it doesn't create an Event Log entry, but it will record in the NPS accounting logs.
When creating your Network Policy, start at the widest breadth - only one condition. Make sure it works, then add another. Same for any constraints. Get it working at the lowest level, then build additional complexity.
*Source*
I'm running two NPS on Server 2016 with two network policies, including one that is only client IP (used for health monitor) and one that is a bit more extensive. The client IP one had the same issue until I changed the condition.
DeeRex Thanks. Will have to look into this in the near future - got a lot going on right now.
Will update once done.
mmendozaf - unfortunately, I have not been able to revisit this yet. Have a look at what DeeRex wrote and see what you can do? I might only get a change to look into this in a couple of weeks. But, I will definitely post any updates on here.
I've had a similar issue myself setting up NPS on Server 2016, originally thought it was because I was exporting our old NPS Configuration from a 2008R2 box, but still happened on a different server on a fresh setup.
I would recommend having a look at those NPS Audit Logs, usually in C:\Windows\System32\LogFiles\ and in particular look at the "Reason-code" field right up the end of an entry. I was receiving Reason Code 22, which seemingly relates to not having a CA certificate installed on the local client. On a lark I checked the Personal Computer Certificates on the NPS server and found that it didn't actually have one. I generated a new one, tried to connect to the RADIUS WiFi network and it worked.
Though I am still running into some issues with NTRadPing, eh.
