asked on

Unable to join workstations to a new domain

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

E C

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?

SOLUTION

Lee W, MVP

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

arnold

Where is the workstation getting its IP from . Make sure the workstation does not have any reference to any external name server
Configure the network to only point at one of the Dcs for name server.
Then try again after you confirm,
nslookup -q=SRV _ldap._tcp.dc.youraddomainname

If you get no answer, this means you have an issue with DNS.

SOLUTION

Hello There

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

CompProbSolv

Comments above on DNS are an excellent start. 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).

Leigh Thorup

ASKER

I ran nslookup -q=SRV _ldap._tcp.dc.youraddomainname and received this:
DNS request timed out.
timeout was 2 seconds
Server: unknown
Address 192.16.1.98
DNS request timed out.
timeout was 2 seconds
DNS request timed out
timeout was 2 seconds
*** Request to unknown timed out

I noticed that the IP address for the DNS server shows a number missing it should be 192.168.1.98. I checked the static IP on the interface and it is correct. How do I fix this query so it is looking for the correct IP address?

SOLUTION

E C

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

ASKER CERTIFIED SOLUTION

Leigh Thorup

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

CompProbSolv

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. The first two got you looking at DNS and Hello There was correct about it being a switch issue.

Glad to hear you resolved it!

E C

seriously.

Leigh Thorup

ASKER

your right a lot of thew answers were helpful.

thanks,

Leigh