To customise your favourite (allowed vs disallowed) Windows Security Protocols, you'd generally end-up mucking around the Windows Registry (specifically at HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders).
Luckily, I remembered what I was working on BEFORE 802.1X stopped working and, more specifically, I was trying to further secure (" micromanage") which Windows Security Protocols were allowed/not allowed (on a Network). In this specific case, the issue that I had with NPS was that it didn't authenticate "Domain User" + "Password". That was the case in point - I experienced an issue with Network Policy Server (NPS) and 802.1X ("Secure Wireless Connections"), which ended wasting a lot of my "family"-time.īut IT hasn't to be that way - you either love solving puzzles or you don't!
Sometimes troubleshooting an issue could end up becoming a never-ending nightmare. This way NPS Secure Wireless Connections (with Domain Username + Password) functionality was restored/Started working again. The solution, in my specific case, was to:
0 kommentar(er)
