Clients Having Login Issues on Server 2025 DC - Need Help!
Asked by
CleverKoala82
I'm having some trouble with our Server 2025 Domain Controller setup. We also have a second Domain Controller running 2022, so we could roll back if necessary. Initially, everything seemed fine, but recently we've noticed that client PCs randomly can't log in after booting up. They enter their credentials, but get an error saying the username or password is incorrect, even though we know the credentials are right. If they reboot their computers, they can log in without issues afterward.
I'm not sure if this is a problem with the Server 2025 DC or the Windows 11 24H2 version. I've come across some discussions about similar problems, but no solutions. I'm currently trying to install the latest September cumulative update on the DC, but I'm not optimistic about it solving anything. Any advice would be hugely appreciated!
Answers
Could be a DHCP issue causing the DNS to be configured incorrectly. Maybe there’s a rogue DHCP server messing things up?
Reply to this answer
When you restart, does the machine connect to the 2022 DC or another one? Figuring that out might help. Have you tried shutting down the 2022 DC to see what happens with logins then?
Reply to this answer
Sounds like a flaky Domain Controller. Check your logs for any collisions or conflicts that could be causing these problems.
Reply to this answer
Have you checked the security hardening changes in the Server 2025 Active Directory? They’ve made some significant updates, like disabling RC4 and modifying how encryption types are managed. It’s a good idea to review these changes to make sure your users and computers are compatible with 2025.
Reply to this answer
There have been a lot of reported issues with Server 2025 this year. We decided against deploying it for new servers because of all the bugs and bad patches we’ve seen.
Reply to this answer
Add your answer
Answers are reviewed before publication.
CleverKoala82: I've gone through quite a few of the changes already. I’d prefer to resolve this instead of downgrading to 2022, as I know I’ll need 2025 eventually.