Connection to Domain Controller - Network Path not Found

[VirexenGroup]

Hi,

I am trying to connect my Windows 10 PC to my DC, I have my DNS configured correctly. When I try to connect this PC I see the "Network Path not Found" error.

I believe this is something to do with my home network router as when I connect my computer to my mobile hotspot I can connect to the domain with no errors. However, I have managed to connect a MacBook to the DC on the same network with no hitch.

So I believe this is something to do with different settings on Windows and MacOS for this network. I can not for the life of me figure out what could be wrong.

The router is a FRITZ!Box 7530 AX (https://en.avm.de/)

Any help in this matter is appreciated. 

[#2]

I'd check to make sure the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS.      

[#3]

My DC has 127.0.0.1 listed for the DNS, the MacOS device connected to the DC from the same network with no issues. I will check the windows DNS settings again.

[#4]

Your domain controller should have it's own static ip address listed primary and loopback (127.0.0.1) listed as secondary.     

[#5]

I have changed this to include the loopback, still seeing the same error. But can connect when connected to my mobile hotspot via wifi.

[#6]

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on **any** domain controller)
ipconfig /all > C:\%computername%.txt (run on **EVERY** domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)

Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

then put `unzipped` text files up on OneDrive and share a link.  

[#7]

https://edivu-my.sharepoint.com/:f:/g/personal/stewart_mccafferty_virexen_com/EgPfqO4kWF5Ag26BMFZ5tN...

[#8]

There appears to be an IPv6 DHCP server (most likely router) on network that will be problematic if not configured correctly. Simplest solution would be to turn off the IPv6 DHCP server. The problemworkstation.txt was cut off so couldn't tell anything there. I did not look at other files because of the above problem. After corrections if problems persist then put up a new set of files to look at.         

[#9]

@Dave Patrick I have turned this off with no luck.

[#10]

Please put up a new set of files to look at.    

[#11]

@VirexenGroup just checking if there's any progress or updates? please don't forget to mark helpful replies.    

[#12]

@Dave Patrick, sorry still no joy I have just completed an reset of the computer to start from scratch with no joy. It seems to be an issue with my home network.

[#13]

@Dave Patrick - It would appear that my ISP block the ports between 135-139 on UDP and TCP, at the outside of our gateway servers. I also cant seem to connect to port 455 from this PC. I am wondering if this could be the issue?

However, how was the MacBook able to connect on the same network... 

[#14]

---

It would appear that my ISP block the ports between 135-139 on UDP and TCP, at the outside of our gateway servers.

---

None of this matters as domain communications do not require this. The main issue was the rogue IPv6 DHCP server (router) on your network.        

[#15]

@Dave Patrick no matter what I do it’s still not working it’s nothing to do with the iPv6. I can connect macOS devices on the same network to the DC and if I add a VPS to the problem machine it seems to work. I am unsure what’s going on. 

[#16]

Sounds good then without the new set of files we have no clues.