Yesterday I hit a reasonably strange problem, which took me quite some time to resolve, long enough, in fact, to prompt me to post this in the hope that anyone else encountering can avoid the circuitous route I took!
Windows 7 system unable to browse local domain resources (file shares etc) but access to Internet was fine. Was able to ping all local servers and DNS functioned correctly. Decided to remove system from domain and re-add. Upon attempt to re-add process was as normal, including request for domain administrator username & password, but despite using correct credentials, domain join would fail with message:
“The following error has occurred when trying to join the “xyz” domain: network path not found.”
Tried (try in order below as one of these may fix for you);
i) Checked that other Windows 7 systems could leave & rejoin domain. (They could, so it was clearly a machine specific issue)
ii) Reboot, followed by Disabling & Enabling NIC, followed by reboot.
iii) Check that current network is set to “Work” type /category.
iv) Disabling Windows Firewall (or other firewalls) & any anti-virus / anti-malware, (remember to re-enable!).
v) Using another NIC (in this case WiFi).
vi) “Removing” NIC from Device Manager & rebooting.
vii) Removing system’s old account from Active Directory “Computers” container.
viii) Reinstalling TCP/IP stack. (netsh int ip reset in command prompt as admin)
ix) Remove & re-add “Client for Microsoft Networks” Client.
x) Run “sfc /scannow” from an elevated command prompt.
None of these fixed it for me and so was just considering a re-install, however I first tried the following, which did work!
- Remove ALL “Clients” / “Services” / “Protocols” from NIC (except IP4 & IP6 which are non-removable and would have been fixed by step “viii”, above, if they were the problem)
- Reboot and re-add the above (this included, in our case, a “minimum working set” of; “Client for Microsoft Networks”, “Link-Layer Topology Discoverer Responder” & “Link-Layer Topology Discoverer Mapper I/O Driver”)
- Following their removal, rebooting & their re-addition, the system was able to join to domain as normal!
Hope this helps someone avoid my pain and as ever, feedback is appreciated on additional options / extra steps etc! 😉
What a pain! I assume you don’t know what caused it to fail in the first place?
99% it was a corruption of one of the NIC drivers / service drivers.
I seemed to have caused this exact problem by doing “vi” above while trying to resolve an intermittent wireless network dropout.
Removing the clients, services, and protocols, then rebooting, re-adding, then rebooting again, I reconnected to my domain automatically.
If you are using a DC under linux (samba 3 or 4), make sure that the daemon “smbd” or “smbd4” are running; besides the deamons “samba4” and “winbindd”. That caused the problem for me, the credentials of the DC admin could be verified, but without “smbd” joining the domain failed.
Thanks for that. Useful to get the Linux angle! 🙂
Had the same problem today (hence the landing here from Google…) – however, it was a client-side application firewall from Sophos that was blocking traffic. Had to set the primary location and then unblock all traffic from this location to be able to join to the domain and/or read shares.
I noticed this when it, like the IPv4/IPv6 above, couldn’t be removed from the NIC….
Thanks for the heads up Jon. May well be very useful heads-up for anyone else in your position.
Solution ix worked for me. Removing the clients, services, and protocols, (except IP4 & IP6 which are non-removable and would have been fixed by step “viii”, above, if they were the problem), then rebooting, re-adding, then rebooting again, I ran the http://connect & then reconnected to my domain automatically.
thanks a million for the time saver:)
Good to know Mike! Thanks for the heads up. 🙂
Thank You! Thank You! Thank You! It worked for me too! (windows 7 64bit)
Had this exact issue, thank you for posting this information but none of these potential solutions worked for me.
I eventually resolved the issue after exhausting all these options (and more) by running “sfc /scannow” from an elevated command prompt.
If i had more time i would review the sfc logs for clues at to what exactly fixed this but hopefully this is enough to maybe help someone else.
Thanks Ray, I think I’ll add that in as an “official” step to the list. SFC is one of the staple options to have on any list when troubleshooting Windows…
For future reference, this worked for me:
Thanks to Jon for the answer I needed and Richard for the page I found it on!
Thank you. I finally could solve a problem like yours using your method.
I’m almost sure that in my case the problem was caused by a Siemens software which adds a network protocol to the TCP/IP v4 stock, but even after uninstalling the software the problem remains the same. Using your method now it is working ok.
Uninstalling AVG fixed it for me.
Richard, You are a life saver! Been working all day on this trying all the other suggested solutions but to no avail! Trying to join a Windows 7 Pro (32 bit) laptop to Windows Server 2012 Domain and kept getting the network path not found error. Your solution did the trick and now the user and I are happy! I was pulling my hair out so thank you for keeping me from going bald and shaving my head!
great instructions, only step that i have to add is to untick the “avg network filter driver” in the network adapter properties. maybe if i had done that first it might of worked straight away.
Oh my god, this worked. After searching for ours in several forums, your tip to remove all of the clients/services/protocols did it.
Thank you man.
Disable temporarily any third party antivirus and firewall and try to join the domain again – That’s it – 🙂
Thanks works for me! 😀
Terry Mcgonigal led me to the correct solution. Sophos Client Side Firewall was the culprit.
Thank you! This literally saved my life!
The step by step worked, thank you sir!
I ran into this after migrating from 2008 R2 DC to 2012 R2. Tried all steps in this article and more (burflags, etc), but the final step solved it. Make sure to capture settings. BTW this was a lab with only one DC. Haven’t had any problems since.
it was — Remove ALL “Clients” / “Services” / “Protocols” from NIC (except IP4 & IP6 which are non-removable and would have been fixed by step “viii”, above, if they were the problem)
Number iii worked for me.
[[[[ iii) Check that current network is set to “Work” type /category.]]]]
Just wanted to say thanks for writing this article. I ran into the problem on another PC, and got frustrated because I couldn’t figure it out. Did a bunch of research, and just set the PC aside because I didn’t have the time to figure it out. Issue popped up on another PC today, found your article and fixed the issue by re-installing all “Clients” / “Services” / “Protocols”.
It doesn’t make sense, but it’s working again. Thank you.
This has also worked for me after a frustrating 3 hours spent on other solutions
After many hours of trying things, what finally worked for me was mentioned on another site buried in the comments, which said: “make sure the following services are started on the workstation: Workstation, DHCP Client, DNS Client, Server, TCP/IP Netbios helper, Computer Browser ”
I was missing the TCP/IP Netbios helper service and copied the registry key lmhosts from a working system and imported the key. Reboot. Voila!
Wanted to add it here to your already excellent list of things to try. Thank you.
This fix definitely works thank you…. The problem I still have is that is not the root cause. Here are my symptoms… Anyone have any idea of the root cause?
Users are unable to connect to network resources with resources mapped from group policy, however they can ping, and DNS resolves no problem with NSLOOKUP.
Running a gpupdate /force, we see an error in RSOP that states group policy mapped drives failed because the workstation service is not running. After further review because the workstation service fails, so does many other services.
A thought was to readd the computer to the domain to reset the secure channel, however when you try to add the computer to the domain it throws the error that “the network path cannot be found.”
This brought us to this article.
-In troubleshooting, we removed AV completely and made sure Windows Firewall was turned off
-All the computers we seem to find are older hardware have an older image.
-DCs don’t have any errors in the logs.
Anyone have any further information. We have 300 users, just hoping it doesn’t happen to each one at a time. This fix works but it is not easy to do remotely.
Record in DNS on AD is pointing to different Ip than your NIC IP, remove record from DNS on AD, Clean cash and restart dns service on AD and should work.