Authentication failed due to a user credentials mismatch. either the user name provided does not map to an existing user account or the password incorect

StefanV 11

Hi all,

I have strange problem in my network/server environment.
When users try to connect to company network (both Wired and Wifi) they can't authenticate to network ( Event ID: 6273, 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 incorrect. )
I am solving this problem when I connect them on interface without authentication, they get network connection to company network and after that they can authenticate on both wired and wifi network which demand authentication.
This is temporary solution until I find a permanent.
This problem appears randomly to users. One day first 2-3 users have this problem, another day another 2-3 users have problem and so on.
My NPS works on Windows Server 2016.

Is anybody had similar problem and anybody know how can I solve it ?

Thanks in advance

fmouche 1 Reputation point

2022-08-11T09:03:43.253+00:00

Hi,

I confirm I have similar problems after installing KB5016681 on my 2012 R2 DC with NPS role. All remaining Windows 7 clients can't connect anymore and I see Event ID 6273 with Reason Code 16 in the NPS log.

Best regards.
Mark @ LMFJ 1 Reputation point

2022-08-31T17:36:08.78+00:00

I am experiencing the same problem, since installing updates around August 4th or 5th. A reboot (not even a NPS service restart) solves the problem for us for about 8-10 hours. I'm about to put a restart server automated task in to happen every 6 hours for the next few weeks.
Nowicki, Eric 11 Reputation points

2022-09-16T03:00:46.127+00:00

Mark,
You are not alone. We are also experiencing this same behavior. It started for us just yesterday AM and a full restart of our NPS server was required to get it working again.
-E
Nowicki, Eric 11 Reputation points

2022-09-23T14:20:45.267+00:00

Hey Mark,
As a follow-up. We found that the certificates on the NPS server had different issuing dates, and 2 of the 3 had "Pre-KB5014754" internal CA certs missing the new non-critical extension with Object Identifier (OID) (1.3.6.1.4.1.311.25.2). Once we "renewed with new keys" all the certs on the server and restarted - we haven't seen any more issues yet (knock on wood).

Hope that helps.
-E
Nowicki, Eric 11 Reputation points

2022-10-11T13:15:17.567+00:00

Appears the root cause of this problem is related to NPS trying to authenticate to an RODC in the same site. The Domain Controller does not appear to redirect/forward the authentication request correctly to a writeable DC and just "Fails Authentication".

We moved all RODCs out of the AD sites running NPS services and this problem has gone away.
Jamie McFarling 31 Reputation points

2024-01-22T16:01:00.01+00:00

@Eric Nowicki , did you move via AD Sites and Services, and you moved the RODCs into other sites without issue or repercussions? I'm contemplating moving our RODC into a newly created site for just the RODC, and still replicate from the site WDC where the RADIUS server resides...
Nowicki, Eric 11 Reputation points

2024-01-22T16:39:29.16+00:00

Correct. Once we provisioned a "dedicated subnet", we simply added that /29 to Subnets under AD Sites and Services, made a New Site, and moved the RODC into it. We didn't experience any problems with auth or replication as we still have full routing established between the previous network and the new dedicated one. NPS/Radius authentication has been stable since making this change.

2 answers

Jamie McFarling 31 Reputation points

2024-02-01T19:28:20.61+00:00

So, following up on @Eric Nowicki 's findings, we shut down our RODC that's in the same AD Site that the RADIUS server is in. We're actually going to demote the RODC and premote it again to a WDC, or build a new DC and promote that to a WDC to replace RODC. Nice work Eric, your findings helped us narrow down the issue!
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Karlie Weng 18,521 Reputation points Microsoft Vendor

2022-08-18T04:20:40.79+00:00

Hello @StefanV

Did you make any new configurations or updates recently?

If it is caused by new updates, usually it gets resolved through future release.

You could report the problem directly to Microsoft via the Feedback Hub:
https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332

Changing the Registry may help, you could refer to a similar case : nps-stopped-working-after-may-2022-updates.html

Other reference document:
advanced-troubleshooting-802-authentication

Best Regards
Karlie

----------

If the Answer is helpful, please click Accept Answer and upvote it.
Please sign in to rate this answer.
StefanV 11 Reputation points

2022-08-19T10:30:31.677+00:00

Hello Karlie,

I have had already this problem 2-3 month, and since the problem occurred until now I installed 2-3 new updates.
I changed and registry from link above but without success.

I mentioned that error on clients machine which can't authenticate is "A fatal error occurred while creating a TLS client credential. The internal error state is 10013." (Event ID 36871).

BR

Mark @ LMFJ 1 Reputation point

2022-08-31T17:37:58.933+00:00

Karlie,

...and when the feedback hub app does not exist on our computers or servers, what is the next avenue to report this issue without creating an invasive, spammy, unnecessary Microsoft Store account on company computers with minimal software install sets?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Authentication failed due to a user credentials mismatch. either the user name provided does not map to an existing user account or the password incorect

2 answers

Your answer