I'm dealing with an issue related to Network Policy Server (NPS) redundancy. I've set up NPS on one domain controller (DC) with a valid certificate from our Certificate Authority, and the client also has a valid cert. My Aruba Mobility Master is configured properly, and all shared keys are correct. When I connect to the initial DC, everything works fine.
However, I exported and imported the configuration to another Windows 2022 DC that also runs NPS. This new DC has valid certificates too. Initially, I had a problem with the shared secret on the Aruba, but I've resolved that issue.
Now, I'm encountering an error where the client can't connect to the network, and the server shows a validation problem. The error logs state that the authentication failed due to a user credentials mismatch, but I've double-checked everything, and all certificates and configurations are in order. Here's the summary of my setup:
- Connection Request Policy Name: Mobility EAP
- Network Policy Name: Secure Wireless Connections
- Authentication Provider: Windows
- Authentication Server: DC2.XXXX.LOCAL
- Authentication Type: PEAP
- Reason Code: 16 (indicating a user credentials issue)
Any ideas on what might be causing this?
2 Answers
Ensure both domain controllers have the same updates installed. There were critical requirements related to OIDs and SIDs that were enforced after September. It's worth checking this to rule out any discrepancies.
Are you aiming to use EAP-TLS for certificate authentication on the client machine? That could be a part of the issue if configurations aren't matching up.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures