PENDING Cannot Join Computers to Domain due to Network Path Not found error

[Kelvin Galabuzi]

I have an Issue joining all my computers to the domain.This is what I have done in my troubleshooting so far.
1.Disabled the Windows firewall on all the computers
2. Restarted the TCP/IP Net Bios Helper service and Remote Registry Service.
Note:
I'am thinking it's a problem with my DNS server but I can successfully remote into the PC's and also perform successfully the nslookup functions - "I dont have a reverse lookup zone setup."
When I create file shares I cannot access them.
The way my Infrastructure is set up is that I have a Hyper-V host providing One External Virtual Switch and this is the same switch my Domain controller connects to as well as one SCCM server.
The Other clients are Hosted on a VMware workstation using Bridged network adapter connecting directly to a D-Link dummy switch.
All of them cannot join the Domain to this lab I have setup
Clients are running Windows 10 1803.
And Servers running Windows Server 2016.

 

[Prajwal Desai]

What is the DNS server and gateway address that is specified on the client machines ?.

 

[Kelvin Galabuzi]

I'am using the domain controller which has the DNS server and it's IP address on the client computers.
DNS Server address-198.162.10.1
Default Gateway-192.162.10.1

Client 01-192.162.10.4
Client's Preferred DNS Server-192.162.10.1

I set the addresses statically.

 

[Kelvin Galabuzi]

I got the problem resolved by resetting my Hyper-V External Virtual Switch.I did this by first converting the Switch to Internal Type then Converting the Switch back External Type.After that it displayed the usual DNS cannot be found error the first time I tried to join the PC's to the domain and then the second time it went through well.This happened on all the clients.

 

[Syed Hasan]

Same issue in my network , I have one physical Active directory server running on Dell R710 and second one is running on ESXi 6.5 , first I have installed DC on physical server (with team the four network cards using Microsoft team feature) , when I start join windows 10 and server 2016 machine they can not join to the domain than I install second ADC and transferred all role in to VM ADC but still facing the issue, than i remove team in physical server and configure only one network interface as fix but still facing the same issue.

Please guide me its urgent.

 

[Luca Co.]

Same issue in my network , I have one physical Active directory server running on Dell R710 and second one is running on ESXi 6.5 , first I have installed DC on physical server (with team the four network cards using Microsoft team feature) , when I start join windows 10 and server 2016 machine they can not join to the domain than I install second ADC and transferred all role in to VM ADC but still facing the issue, than i remove team in physical server and configure only one network interface as fix but still facing the same issue.

Please guide me its urgent.

Hi, I have the same problem, how did you solve it?

 

[Sam Banford]

I know this one's a bit old but unless you have some kind of routing setup on the DC it should not be set as the default gateway. Default Gateway isn't an alias for "the DC" or "the main computer" it's a device that's configured to route network traffic to other networks, DC's don't natively do this.

Most of us on here speak in terms of a test/home/vm environment where all systems are sitting on the same subnet using a virtual switch or home router. Unless you have your systems all connected to the internet (kind of a bad thing) the default gateway should be blank. An exception to this would be a WSUS server that's dual-homed in which only the external NIC has a gateway (set to whatever it is that can get out); having 2 DG's is also bad.