A domain controller could not be contacted for the domain that contains an account for this computer

So the domain does have other DCs online?
And they are of course 2003 functional level?
How exactly did you run dcpromo?
Have you tried dcdiag to clean up problems?
Where are the FSMO roles?
One issue I've ran into when removing 2003/2008 DCs for 2012 or newer ones is with GPOs becoming lost. Please remember to backup all GPOs before demoting any domain controllers. This will save you. I also recommend ensuring your DC's are syncing correctly and first transfer all FSMO roles to the new domain controllers.
If all else fails, start perusing the event logs to see what happened on the demotion.
Now I tried dcpromo /forceremoval
Then its worked & removed active directory domain
I just want to remove the server 2003 replace with server 2019 & will keep server 2003 as client pc of server 2019 means i will join the server 2003 to server 2019 domain
check if you are member of enterprise/domain/schema admin groups.Check the dns setting has proper DNS IP assigned
Sikander2640 wrote:

I just want to remove the server 2003 replace with server 2019 & will keep server 2003 as client pc of server 2019 means i will join the server 2003 to server 2019 domain

What are the current DCs OS(es) and what is your Domain Functional level ?
There is no direct path for DC2003 (DC2008) to DC2019....so demote may have errors.
I tried on vmware, everything is working now.
Prior to demoting windows 2003 DC make sure all the services are transferred to other DC's in the domain like GC, DNS,DHCP if at all it also holds FSMO role.
Transferring FSMO roles: https://www.petri.com/transferring_fsmo_roles
Make sure that each DC/DNS server is pointing to itself as primary DNS server and to other internal DNS servers as primary ones.Restart netlogon service.After that, make sure that the server to promote is pointing to an internal DNS server as primary one and run dcpromo again.If that doesn't wotk then you will need to run:dcpromo /forceremoval
Follow this with a metadata cleanup: https://community.spiceworks.com/how_to/132621-how-to-perform-metadata-cleanup-in-active-directory
Have you checked your DNS settings? that could cause an issue when trying to promote or demote a domain controller.

While connecting to a domain or changing the computer name, if you are getting An Active Directory Domain Controller (AD DC) for the domain “domain-name.com” could not be contacted error, here are some troubleshooting tips and tricks to fix this issue. It may appear due to a typing mistake or some other internal issues. Either way, you can fix it by following these guides. The entire error message says:

An Active Directory Domain Controller (AD DC) for the domain “domain-name.com” could not be contacted.Ensure that the domain name is typed correctly.
If the name is correct, click Details for troubleshooting information.

The Details menu doesn’t always help you fix the problem, and that is why you should follow these tips and tricks to get rid of it.

To fix An Active Directory Domain Controller (AD DC) for the domain could not be contacted, follow these steps:

Check Ping status
Add domain controller IP in DNS list
Don’t use Public DNS
Start DNS Client service
Join device to local Active Directory domain

To learn more about these steps in detail, you need to keep reading.

1] Check Ping status

It is probably the first thing you should check to ensure that the domain is currently online or not. If the domain is not up for you, you cannot connect to it by following any method. Therefore, do the following to check if you can get a positive ping result or not:

Press Win+R to open the Run prompt.
Type cmd and press the Enter button.
Type ping domain-name.com and press the Enter button.

If it shows ping results with multiple and continuous replies on the Command Prompt window, you can go ahead with other solutions.

2] Add Domain Controller IP

The host and all the other computers should carry the same DNS servers to be connected to a Domain Controller. However, the computer shows the aforementioned error message; it is most likely causing due to the wrong DNS servers. To confirm that, do the following:

Press Win+R to open the Run dialog.
Type ncpa.cpl and hit the Enter button.
Right-click on the Ethernet and select Properties.
Double-click on the Internet Protocol Version 4 (TCP/IPv4).
Make sure you have the correct IP address, Subnet mask, and Preferred DNS server.
If not, ask your admin to provide the correct details and enter them accordingly.
Click the OK button to save the changes.

After that, you should be able to ping the domain and connect to it.

3] Don’t use Public DNS

Using the Public DNS will create more conflict when you try to connect to a domain. Many people often tend to use Public DNS in the place of Preferred DNS server and Alternate DNS server.

You need to be using the DNS server that your administrator has provided. If you are the admin, you need to use the DNS server details the same as the Domain Controller or the host computer.

4] Start DNS Client service

DNS Client service needs to be running in the background in order to use any DNS server on your computer. If by any chance, it is disabled or stopped, you may come across this problem. Therefore, do the following to verify the service is running or not:

Search for services in the Taskbar search box.
Click on the individual result.
Search for the DNS Client service and double-click on it.
If the status is Stopped, click the Start button.
Click the OK button to save the change.

After that, restart your computer to check if it resolves the issue or not.

5] Join device to a local Active Directory domain

When you try to add a Work or School account, it offers an option to add or join the device to a local Active Directory domain directly. You can use this option to solve your problem. For that, follow these steps:

Press Win+I to open Windows Settings.
Go to the Accounts section and click on the Access work or school menu.
Click the Connect button.
Click on the Join device to a local Active Directory domain option.
Enter the domain name and click the Next button.
Enter the administrator username and password.
Enter the account information and choose the Account type.
Restart your computer.

After restarting, your account and computer should be added to the domain without getting the above-mentioned error message.

How do I fix my domain controller DNS?

To fix the domain controller DNS issue, you need to enter the correct DNS server details in the Network Connections panel. You should not be using any Public DNS either.

How do I connect AD domain controller?

To connect to an AD Domain Controller, you have to enter all the correct DNS servers in the Network Connections panel. Secondly, you can open the System Properties panel, click the Change button, switch to the Domain menu, and enter the domain you want to connect to.

That’s all! These are some working solutions to fix AD Domain Controller issue.

Related:

report this ad

Sudip loves to engage with the latest technology & gadgets. Apart from writing about all things technology, he is a Photoshop junkie and a football enthusiast.