Windows
Windows sign-in could not find the domain; account was disabled and passwords were resynced
The user could not sign in because Windows said it could not find the domain. The technician used a local admin account, connected the VPN, re-enabled the disabled account after confirming the change was intentional, and reset the AD password to match the new Microsoft account password so sign-in worked again.
Killed once by someone from XL.net, on 2025-09-29.
Affects
Apps
- Outlook
- NetSuite
- VPN
What you see
- Sign-in fails with a message that the domain cannot be found.
Why it happens
Likely The account was disabled, and the Active Directory password needed to be brought into sync with the Microsoft account password used for email and VPN access.
When it shows up
A remote Windows user cannot sign in and gets a domain-not-found message, but a local admin account still works and VPN access is needed before the domain account can be used.
You are in this case if:
- Exact sign-in message says the domain cannot be found.
- The affected account is disabled in directory administration.
- A local admin login can still be used to reach the machine, then VPN is required before the user account will sign in.
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Someone from XL.net killed this on a Windows computer on 2025-09-29. It is written up from that one repair, so it cites no outside page.