Before anyone says "don't use PAP", yes yes I know. But, our Dell 6000 series network switches only support PAP. :-(
On the 16 May PAP authentication on the switches worked perfectly.
By 24 July it had stopped working. (Yes, we don't log into them very often because they just work.)
We have checked the switch configs - nothing's changed in config / firmware etc.
We have checked the NPS server config - no changes there either.
Well, something's obviously changed, but I can't see what.
A bit of background...
NPS reports this:
Authentication Details:
Connection Request Policy Name: Dell 6248P Switch Management CRP
Network Policy Name: -
Authentication Provider: Windows
Authentication Server: WIMNPS01.v1c.biz
Authentication Type: PAP
EAP Type: -
Account Session Identifier: -
Logging Results: Accounting information was written to the local log file.
Reason Code: 16
Reason: Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.
The domain controller says this:
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: a.admin.user
Source Workstation:
Error Code: 0xC000006A
So, we can see that the DC is simply rejecting the request. (The NPS debug logs really just confirm this: they'll all paraphrases of "the DC says 'no'"! So, I'm not bothering to dump them here.
The mystery is: why is the DC suddenly saying "no", when, back in May, it (correctly) said "yes"?
NPS: 2012 R2 (fully patched)
DC: 2016 (fully patched)
The Domain is replicating perfectly.
I'm wondering: I know how Microsoft like to release security patches that break things / make them more secure (take your pick). So before I do some serious debugging on the DC (which is going to take ages), I was wondering if anyone's reading this thinking"this is a classic - PAP on NPS against a 2016 DC no longer works"? Or something.
(I have cleared the NPS config and re-created it - didn't fix it.)
(Oh, and yes, the password is definitely correct! The problem affects all network admins.)
TIA
m