Unable to Logon to Win2003 Domain AD Due to Windows Cannot Connect to the Domain Error
The computer and user account has been created and existed in a Windows 2003 domain Active Directory (AD) where a domain controller (DC) running Microsoft Windows 2003 Server opeating system. However, you may encounter the following error message when a domain user tries to autheticate and logon to the domain from a workstation which can be running on Windows XP (with or without SP2) operating system or any other OS:
Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance.
The symptom or error may appear when a PC is replaced with another computer with the same computer name without first deleting the duplicate computer name from the domain Active Directory service before joining the new workstation to the domain with that duplicate name. The symptom may appear immediately or after a few successful log-ons. The cause of the error will probably due to security identifier (SID) issues. Another possible cause for the error is that the computer account for the workstation is accidentally deleted.
The resolution and workaround to solve the above error in above condition is as below.
- Login to the Windows 2003 domain controller, and delete the computer account object from the Active Directory by using Microsoft Management Console (MMC) which you can always access from “Manage Your Server”.
- Log-in to the PC workstation as local administrator. If you cannot logon as local administrator, try to unplug the network cable and logon to the computer by using a domain administrator user that used to logon on the PC before, by using cached logon credentials feature.
- Go to Control Panel, then click on System icon, then go to Computer Name tab.
- Unjoin the computer from the domain by clicking on “Change”. You should see that Domain button is now selected. Remember your domain name in the text box. Select (Click) on “Workgroup” to remove the computer from the domain, and put any workgroup name in the text box (e.g. workgroup).
- Click OK to exit.
- Restart the computer (optional)
- Go back to the Control Panel, launch System properties and then go to Computer Name tab, and click on “Change”.
- Rejoin the domain by uncheck the Workgroup button and select (check) Domain button, and put in the domain name noted above into the text box.
- Click OK to exit.
- Reboot the PC.
This should solve the unable to logon to domain error, without changing or losing the user profiles on AD.
Related Articles
- How to Enable Auto Logon to Windows XP and Vista Joined as Domain Member
- Hack and Reset Windows NT 4.0 and Windows 2000 Administrator or Domain Admin Password with LOGON.SCR Trick
- Microsoft Money 2007 Unable to Connect to Internet to Sign In Online in Windows Vista Error
- OFXIE12007 Microsoft Money 2007 Unable to Connect Error
- Unable to Connect to Internet in Virtual PC with NAT Shared Networking NAT on Windows XP Guest
- Tweaking Windows XP Logon Screensaver and Logon Message Box
- Unable and Cannot Connect to WPA and WPA2 Encrypted Wireless Wi-Fi Network in Windows XP
- Domain Does Not Have Any NS Records Error at DNSStuff.com or DNSReport.com
- Unable to Login to Windows Live (MSN) Messenger with 80048820 Extended 80048416 Error Code
- Enable Automatically Logon/Login Into Windows XP
Entries (RSS)
November 3rd, 2009 21:38
John presumably feels very high and mighty now, but should probably consider that not everyone who experiences this problem is dealing with a simple Windows XP Pro box. Try involving centrally managed thin clients, perhaps with firmware refreshing going on, and see if you should be the one researching a new profession.
March 17th, 2009 19:08
lol, you can just unjoin the pc from the domain and rejoin. That will fix this issue. He/she is correct about the DC as the problem just not the fastest solution to the fix. If you spent more than 5 min on this problem time to look for a new profession. Have a good one!!
February 3rd, 2009 22:25
AWESOME! Like another poster I burned about an hour and a half before finding this fix. Rock on!
January 3rd, 2009 18:31
I am too tired …. five days later …. but thankyou, thankyou, thankyou …. it worked ! F*@!ing Microsoft !!!!
PS. It shouldn’t be this hard!
October 21st, 2008 17:08
i had same issue with shane.
August 18th, 2008 07:28
Worked great for me! Could have been a huge issue. It was our Terminal Server that had the issue (aprox 50 users) so it would have been a hell if I had not found this before the next work day. Hopefully I don’t have the re-occurring issue like Shane above me has posted…
Many Thanks!
March 27th, 2008 00:14
I did this fix and it work for a little while but then after about a week the same user came back with the same issue. I’ve rejoined the same computer from the domain many times befroe but it keeps coming back. Any one have any ideals?
January 31st, 2008 06:31
Thank you for this great tip. I only burned 2 hours before I found this.
December 27th, 2007 20:30
nice one – this helped me loads – you are the bomb