FIX: The Specified Domain Either Does Not Exist or Could Not Be Contacted (Solved)
This tutorial contains instructions to resolve the following problem, when you try to join a Windows based computer to an existing domain: "The Specified Domain Either Does Not Exist or Could Not Be Contacted".
The error "The Specified Domain Either Does Not Exist or Could Not Be Contacted" commonly occurs due to invalid DNS settings on the workstation's side, because Active directory requires you to use domain DNS to work properly (and not router's address).
How to fix: Specified Domain Does Not Exist or Could Not Be Contacted.
Let's suppose that your Active Directory Domain Controller (and DNS Server) is a Windows Server 2016 machine and is responsible for the domain "wintips.local" and has the IP Address "192.168.1.10".
At this example, the IP and the Preferred DNS address on the Primary Domain Controller (Server 2016) must be the same, e.g.
| Primary Domain Controller (Server 2016) | |
| Computer Name: | Server2k16 |
| Domain Name: | WINTIPS.LOCAL |
| IP Address (Static): | 192.168.1.10 |
| Subnet Mask: | 255.255.255.0 |
| Default Gateway: | 192.168.1.1 |
| Preferred DNS Server: | 192.168.1.10 |
Method 1. Set the Preferred DNS Server Address to match the Domain Controller's IP Address (on Client Workstation)
To resolve the "Specified Domain Does Not Exist or Could Not Be Contacted" error, you have to set the Preferred DNS IP to point to Primary Domain Controller's IP address, on each client workstation that you want to join in the domain. To do that:
1. Open Network and Sharing Center.
2. Right click on Local Area Connection and click Properties.
3. Double click on Internet Protocol TCP/IPv4.
4. Change the Preferred DNS server address to match the Primary Domain Controller's IP Address (e.g. "192.168.1.10" in this example).
6. Click OK twice and close all windows.
7. Try to join the workstation in the Domain.
Method 2. Specify the WINS Server's IP Address on Client.
If your Active Directory Domain Controller acts also as a WINS server, then set the WINS IP address to point to WINS Server's (Primary Domain Controller's IP address),* on the client machine that you want to join to the Domain. To do that:
* Note: This method works even when the Primary Domain Controller does not act as a WINS Server.
1. Open Network and Sharing Center.
2. Right click on Local Area Connection and click Properties.
3. Double click on Internet Protocol TCP/IPv4.
4. Click the Advanced button.
5. At WINS tab, click Add.
6. Type at WINS Server's IP Address filed, the IP address of the WINS server (e.g. "192.168.1.10" in this example) and click Add.
7. Press OK three (3) times to apply changes and close all windows.
8. Try to join the machine in the Domain.
That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
We're hiring
We're looking for part-time or full-time technical writers to join our team! It's about a remote position that qualified tech writers from anywhere in the world can apply. Click here for more details.
- FIX: Not in a hypervisor partition, VT-x is Disabled in BIOS in VirtualBox' (Solved) - April 29, 2024
- How to Disable or Remove BitLocker from Windows RE. - April 24, 2024
- FIX: Error 0x8007025d in Windows 10 Update. - April 22, 2024
July 18, 2023 @ 2:47 pm
Setting DC as Preferred DNS (Method 1) instead of Alternate DNS did the trick, thank you
August 22, 2022 @ 5:14 am
I disabled ipv6 and it worked for me. Thanks all
August 15, 2022 @ 9:00 am
it worked!! thanks :))
July 13, 2021 @ 6:18 am
Worked
July 1, 2021 @ 10:27 pm
Adding the DNS of the Servers IP to the Client workstation Ipv4 DNS settings, worked PERFECTLY! Server 2012 and Windows 10 Pro configuration.
April 30, 2021 @ 12:31 am
This worked. Thank you! Windows Server 2016 AD
September 25, 2020 @ 3:28 pm
Entering the domain controller's IP in the WINS tab on the machinr attempting to join the domain worked for me. Thank you
August 17, 2020 @ 10:24 am
thanks, It works for me
December 21, 2019 @ 9:40 pm
Thanks. Solved my issue!
November 28, 2019 @ 9:25 pm
Try disable IP PROTOCOL VERSION 6
January 21, 2022 @ 9:03 pm
this work for me.thanks
February 12, 2022 @ 8:18 am
Disabling IP6 also worked for me.
November 19, 2019 @ 5:45 pm
Method 1 worked for me. Thanks!!
July 17, 2019 @ 3:35 pm
posted tutorial helped me but having some issue regarding internet access
client got connected with domain controller but not able to get internet access+
July 18, 2019 @ 11:09 am
@chandu: If you domain controller acts as a DNS server, then you have to add your ISP's DNS addresses or the Google's DNS address to Forwarders.