Forum Discussion
NTRadPing gets rejected by Win2016 NPS
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.
