<div>
Assuming the workstations are running Win 10 Pro (not home) this sounds like a DNS issue. Are the workstations using a DHCP server? When you created the domain controllers did you also set up active-directory DNS?
</div>


IT Consultant and MSP

Leigh Thorup

<div>
Where is the workstation getting its IP from . Make sure the workstation does not have any reference to any external name server<br />
Configure the network to only point at one of the Dcs for name server.<br />
Then try again after you confirm, <br />
nslookup -q=SRV _ldap._tcp.dc.youraddomain<wbr />name<br />
<br />
If you get no answer, this means you have an issue with DNS.
</div>


<div>
Comments above on DNS are an excellent start. &nbsp;I'd also confirm that you can ping the DC from the workstation both by number (this will test the virtual switch) and by name (this will test DNS).
</div>


<div>
I ran nslookup -q=SRV _ldap._tcp.dc.youraddomain<wbr />name and received this:<br />
DNS request timed out.<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;timeout was 2 seconds<br />
Server: unknown<br />
Address 192.16.1.98<br />
DNS request timed out.<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;timeout was 2 seconds<br />
DNS request timed out<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;timeout was 2 seconds<br />
*** Request to unknown timed out<br />
<br />
I noticed that the IP address for the DNS server shows a number missing it should be 192.168.1.98. &nbsp;I checked the static IP on the interface and it is correct. &nbsp;How do I fix this query so it is looking for the correct IP address?
</div>


<div>
While I appreciate the points, I think it would be more appropriate to award them to the earlier answers from E C, from Lee W, and from Hello There. &nbsp;The first two got you looking at DNS and Hello There was correct about it being a switch issue.<br><br>Glad to hear you resolved it!
</div>


<div>
your right a lot of thew answers were helpful. <br><br>thanks,<br><br>Leigh
</div>


<div>
<div class="content wysiwyg-content">
I have been struggling trying to figure is issue out. &nbsp;I have a client who we have moved them from a workgroup scenario to a Domain setup. &nbsp;We are using a Dell PowerEdge server with windows 2016 standard on it. Have installed Hyper-V &nbsp;and created two DCs. &nbsp;I am having issues getting the windows 10 clients to join the domain. &nbsp;I keep getting the error 'The network path was not found'. I need to know what troubleshooting I need to get this fixed. &nbsp;Thanks<br />
<br />
Leigh
</div>
</div>


I have been struggling trying to figure is issue out.  I have a client who we have moved them from a workgroup scenario to a Domain setup.  We are using a Dell PowerEdge server with windows 2016 standard on it. Have installed Hyper-V  and created two DCs.  I am having issues getting the windows 10 clients to join the domain.  I keep getting the error 'The network path was not found'. I need to know what troubleshooting I need to get this fixed.  Thanks

Leigh

Unable to join workstations to a new domain

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Since 1984, Dell has been delivering technology to fit your life.
Dell is in Enterprise, Home Office and Consumer sectors of the market, supplying a broad range of customizable desktops, laptops, notebooks, servers, storage, and network devices.

Dell

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.