Unable to Logon to Win2003 Domain AD Due to Windows Cannot Connect to the Domain Error
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.
Windows cannot connect to the domain either because the domain
Hi Ace Fekay / Tiger Li,
Please find below the IP Configuration of My DC 1 (PDC)
Windows IP Configuration
Host Name . . . . . . . . . . . . : adsrv01
Primary Dns Suffix . . . . . . . : hastinapur.res
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hastinapur.res
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-21-5A-A8-27-32
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.16.1.36(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.16.1.10
DNS Servers . . . . . . . . . . . : 10.16.1.36
10.16.1.37
NetBIOS over Tcpip. . . . . . . . : Enabled
Please find below the IP Configuration of My DC 2 (ADC)
Windows IP Configuration
Host Name . . . . . . . . . . . . : adsrv02
Primary Dns Suffix . . . . . . . : hastinapur.res
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hastinapur.res
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . : hastinapur.res
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-21-5A-AA-C9-EC
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.16.1.37(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.16.1.10
DNS Servers . . . . . . . . . . . : 10.16.1.37
10.16.1.36
NetBIOS over Tcpip. . . . . . . . : Enabled
Also I am getting a Warning in event viewer, Please find the details below,
Log Name — DNS Server
Source — DNS Server Service
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
Windows cannot connect to the domain either because the domain
Hi Ace Fekay / Tiger Li,
Please find below the IP Configuration of My DC 1 (PDC)
Windows IP Configuration
Host Name . . . . . . . . . . . . : adsrv01
Primary Dns Suffix . . . . . . . : hastinapur.res
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hastinapur.res
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-21-5A-A8-27-32
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.16.1.36(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.16.1.10
DNS Servers . . . . . . . . . . . : 10.16.1.36
10.16.1.37
NetBIOS over Tcpip. . . . . . . . : Enabled
Please find below the IP Configuration of My DC 2 (ADC)
Windows IP Configuration
Host Name . . . . . . . . . . . . : adsrv02
Primary Dns Suffix . . . . . . . : hastinapur.res
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hastinapur.res
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . : hastinapur.res
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-21-5A-AA-C9-EC
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.16.1.37(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.16.1.10
DNS Servers . . . . . . . . . . . : 10.16.1.37
10.16.1.36
NetBIOS over Tcpip. . . . . . . . : Enabled
Also I am getting a Warning in event viewer, Please find the details below,
Log Name — DNS Server
Source — DNS Server Service
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.