Link to home
Start Free TrialLog in
Avatar of Sheldon Livingston
Sheldon LivingstonFlag for United States of America

asked on

Cannot join domain and UNC paths

I built a new 2016 domain.

When I try and join a machine to the domain I get a "the network path was not found".

Hitting the server via \\theServer also fails.

I can ping the server by name and IP and domain.

Thoughts?
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
What Rob said DNS, check connection, try swapping out the nics, also try joining from another machine -- make sure you're typing in the credentials right
Avatar of Sheldon Livingston

ASKER

Rob... this suffix thing was the issue.  How do I get the suffix to be pushed out by the DNS server automatically?
If using the server as the DHCP server, check the scope options You should configure gateway, DNS server, and Domain suffix.  I forget gateway but I think DNS is option 006, and Domain Suffix is 015, but they are labeled.  If using a router for DHCP, same applies and somewhere there is an option to add domain suffix.  It needs to be internal suffix, like mydomain.local
Actually suffix is under domain name 015.  Attached picture may helpUser generated image
and if NOT using the server for DHCP?  We are using the cable modem.
There is usually a box on the DHCP configuration page of the router/modem named "Domain".  Enter it there and also change DNS so it only points to your server. Routers will automatically assign the ISPs DNS and I guarantee that will cause problems over the years, even if a secondary.

What model unit?  I may be able to provide details.
Sweet!  Suffix was the issue.  I moved the DHCP from cable modem to server.
Glad to hear.  I always prefer using the server's DHCP.  More control, better monitoring of the service, and issues are recorded in the event viewer.

Thanks classnet!