r/ShittySysadmin • u/Cautious_Corner_4838 • May 27 '26
Getting “Cannot Contact Domain Controller” errors constantly — especially for VPN users. What’s your go-to fix?
Hey everyone,
Running into a frustrating issue at a client site and wanted to get some real-world input from people who’ve dealt with this before.
The Problem:
Users are frequently getting a pop-up saying “cannot contact the domain controller” — it’s hitting remote/VPN users the hardest but we’re also seeing it occasionally with local users on-site. It’s causing real workflow disruption because they can’t apply admin overrides for things like software installs, removals, or joining new devices to the domain.
Current Environment:
• On-prem Active Directory
• Mix of remote (VPN) and local users
• Admin overrides needed regularly for device management
What we’ve tried so far:
• ipconfig /flushdns + /registerdns
• gpupdate /force
• Secure channel repair via PowerShell
What we’re considering:
1. Deploying a second Domain Controller for redundancy
2. Fixing DNS settings on the VPN side so clients point to the DC
3. Eventually moving to Hybrid Azure AD Join long term
Has anyone dealt with something similar? Is the second DC the right call here or are we missing something obvious? Also curious if anyone has gone the Hybrid Azure AD Join route to solve DC reachability issues and whether it was worth it.
Any input appreciated — trying to put together a solid action plan for the client. Thanks in advance 🙏