You try to add a new PC to your company domain and Windows stops you with an error: The network path was not found, or An Active Directory Domain Controller for the domain could not be contacted. The PC has internet, the server is running, so what is wrong? In almost every case the problem is DNS. The client PC cannot find the domain controller by name. This guide shows how to confirm that quickly and fix it step by step.

Why this error happens

A domain join is not just a network connection. The PC first asks DNS where the domain controller is by looking up special SRV records. Only the domain controller’s own DNS server knows those records. If the PC uses your router or a public DNS server such as 8.8.8.8, the lookup fails and Windows reports that the network path was not found.

Other less common causes are wrong time settings, blocked ports, a typing mistake in the domain name, and using a Windows edition that cannot join a domain.

Step 1: Confirm basic connectivity

On the client PC open Command Prompt and ping the domain controller by its IP address:

ping 192.168.1.10

Replace the address with your domain controller’s IP. If this fails, fix the network first: cable, Wi-Fi, switch port, VLAN or IP range. The PC and server must be able to reach each other before anything else can work.

Step 2: Point the PC’s DNS to the domain controller

This step fixes the problem in most cases.

Press Win + R, type ncpa.cpl and press Enter.
Right-click your active network adapter and choose Properties.
Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
Choose Use the following DNS server addresses.
Set Preferred DNS server to the IP address of your domain controller. If you have a second DC, add it as the alternate DNS.
Click OK and close all windows.

Do not put 8.8.8.8 or your router’s address here. If many PCs have this problem, the real fix is in the DHCP server. Set DHCP option 006 (DNS servers) to your domain controllers so every PC gets the right DNS automatically.

Step 3: Test name resolution

In Command Prompt run:

nslookup yourdomain.local

It should return the IP address of your domain controller. If it says it cannot find the domain, DNS is still wrong. Then test the record Windows really needs:

nslookup -type=SRV _ldap._tcp.dc._msdcs.yourdomain.local

If you get answers with your DC name, the DNS part is healthy. After changing DNS, clear the old cache and register again:

ipconfig /flushdns

ipconfig /registerdns

Step 4: Use the correct domain name

Try the full domain name (for example company.local) instead of the short NetBIOS name (for example COMPANY). Check the exact spelling on the server. Open Active Directory Users and Computers on the DC and read the domain name at the top of the tree.

Step 5: Check date, time and time zone

Active Directory uses Kerberos, and Kerberos allows only a small time difference, by default 5 minutes, between the PC and the domain controller. Check the client’s date, time and time zone. To compare with the server you can run:

w32tm /stripchart /computer:DC01 /samples:3 /dataonly

Replace DC01 with your server name. If the difference is large, correct the time zone first and then sync the time.

Step 6: Check ports and firewall

The client needs to reach several ports on the domain controller. The main ones are DNS 53, Kerberos 88, RPC 135, LDAP 389 and SMB 445. In PowerShell test them:

Test-NetConnection -ComputerName 192.168.1.10 -Port 445

Test-NetConnection -ComputerName 192.168.1.10 -Port 389

Look for TcpTestSucceeded : True. If a port fails, check Windows Firewall on both sides, any third-party antivirus firewall and any firewall between network segments. Also make sure the PC’s network profile is not blocking discovery in a way that affects it, and try temporarily disabling a third-party security suite during testing.

Step 7: Check the domain controller itself

If several PCs fail, the problem may be on the server.

Make sure the DNS Server and Netlogon services are running.
Run dcdiag /test:dns on the DC and read any failures.
Run net share and confirm that NETLOGON and SYSVOL are listed.
In the DNS console, check that the zone for your domain exists and contains the _msdcs folder and SRV records.
Check that the DC’s own network adapter uses itself (or another DC) as DNS, not a public server.

Step 8: Check Windows edition and computer name

Windows Home cannot join a domain. You need Pro, Business, Enterprise or Education. Upgrade the edition first.
Make sure the computer name is unique. If an old computer account with the same name exists, either use another name or reset the old account in Active Directory.
Keep computer names short and without special characters.

Now join the domain

Press Win + R, type sysdm.cpl, go to the Computer Name tab, click Change, choose Domain, enter the domain name and sign in with an account that has permission to add computers. Restart when asked.

FAQ

Can I use 8.8.8.8 as DNS on domain PCs? No. Domain PCs must use the domain controller as DNS. Put public DNS servers as forwarders on the DNS server so that internet names still work.

Only one PC fails to join. What does that suggest? The server is fine. Check that PC’s DNS setting, time, Windows edition and firewall software.

Does a VPN or Wi-Fi guest network cause this? Yes. If the PC is on a different network or VPN without access to the DC and its DNS, the join fails.

Do I need to disable IPv6? Not normally. Fix DNS first. Disabling IPv6 is not recommended unless you have a specific reason.

Related reading: How to Reset a User Password and Unlock an Account in Active Directory | IP Address Conflict in the Office: How to Find and Fix It | How to Automate Windows Server Backup

The Network Path Was Not Found: Domain Join Error Fix