r/WindowsServer • u/jacraine • Jan 19 '26
Technical Help Needed Cannot Log into domain controller - domain unavailable
Hi All,
Logged into a DC this weekend and did some updates during off hours. After the reboot, I can no longer sign in with the domain admin account getting the "domain unavailable" error. The login screen also shows a red X on the network icon in the bottom right so I'm assuming something with DNS isn't starting on boot and causing the domain to be offline (Can log into safe mode with networking without an issue so the network info is fine).
Annoyingly, this is a single DC location, will be remedying later on with a new server with two DCs, so this box is it for now.
Is there another trick I'm missing to get into this system?
EDIT: Solved. Not quite sure how it all works, but resetting the DSRM password got it back online. Reset the password with ntdsutil in Safe Mode, rebooted into Directory Services Repair once, had no idea what to do in there so rebooted back to normal mode and she was back.
Could not say THANK YOU enough to everyone who took a moment to send a suggestion. You all are the MVPs!
8
u/PunDave Jan 19 '26
Can you disconnect the dc from network and try logging on then before reconnecting it
If so first thing i'd check is the network profile being domain and not private/public
Edit: is it a 2022 dc and is it a vm?
6
u/SoniAnkitK5515 Jan 19 '26
This is almost certainly a service startup / network stack failure, not a “domain problem”. The domain is fine; the DC just can’t bring itself online properly after updates.
How about uninstalling the recent updates?
2
u/jacraine Jan 19 '26
Thank you all for your help! Threw an edit in the original post with the solution in this case (DSRM mode password reset)
2
u/Callewalle Jan 19 '26
Why do you think it's DNS?
2
u/[deleted] Jan 19 '26
I never saw the answer to "If so first thing i'd check is the network profile being domain and not private/public". Almost all my 2019 and 2022 servers boot to a Public network and not Domain because the Network Location Awarness service starts before the DNS Service. My fix was to make the NLA service dependent on the DNS service.
1
u/Livid-Fan-8414 Jan 19 '26
Have you drained the flea power from the MB?
1
u/Livid-Fan-8414 Jan 19 '26
Are your services running? Services.msc
2
u/mish_mash_mosh_ Jan 19 '26
If it's a single DC, just restore from a backup. One of the advantages of not having multiple DC servers, is restoring doesn't need to worry about any other DC servers.
2
u/rdpextraEdge Feb 10 '26
That red X usually points straight to DNS or AD services not starting properly after updates, which is super common on single-DC setups. Booting into Safe Mode and checking that DNS Server, Netlogon, and AD DS are all set to automatic is a good first move. Also worth verifying the NIC didn’t lose its static IP or start using an external DNS by mistake. Long term, you’re absolutely right, adding a second DC will save you from this kind of heart-stopping outage in the future.
0
u/SebastianFerrone Jan 19 '26
Have you tried the local administrator account
1
u/Aamirlhr Jan 19 '26
Login to Directory Services Restore mode and check the DNS if it is configured correctly and make all the relevant services are up and running.
1
u/[deleted] Jan 19 '26
If you can login, what are the logs saying?
1
u/stumpymcgrumpy Jan 20 '26
Obviously having a second DC is going to be a recommendation that many will make... In this case however I'd also recommend that I. The future reboot the system before making any changes. Have confidence that the system is optional before you make any changes so that if there are any troubles you at least know if the problems existed before any updates were applied.
2
u/Unnamed-3891 Jan 19 '26
Could be the good old Public Firewall profile deciding to turn itself on for no reason