(Nope, I don’t know these codes of the top of my head! My colleague who did the troubleshooting came across this. In this case the packet type data of 3 means the access was rejected, and the reason code 259 means CRL check failed. Pro Tip: If you go with the XML format and use Visual Studio code, you can prettify the XML as mentioned here.įrom the logs we could see entries like this: All of this stuff is in the “Accounting” section BTW: Side by side it is also worth changing the format to “DTS Compliant” as that produces a better readable XML output. One option is to change the log format to “IAS (Legacy)” and “Daily” and use a script such as the one here to analyze. That’s when I realized the logs generated by NPS (at C:\Windows\System32\Logfiles) are horrendous. The setup is quite similar to what is detailed here, with the addition of using an internal CA issued certificates for NPS to authenticate the users (as detailed here or here for instance).Īll wireless clients stopped being able to connect to the wireless. We have an internal wireless network that is set to authenticate against Microsoft NPS using certificates. Came across an odd problem at work the other day involving NPS and Wireless APs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |