05-15-2019 09:41 AM
05-15-2019 09:41 AM
I hope you can help. I am trying to connect my windows 10 pro laptop to my windows server 2016 Active Directory Domain and yet when I try to join the domain, the error message is that the domain doesn't exist.
I have made sure I have the following services running:
On the server:
Subnet mask: 255.255.255.0
Default gateway: ***.***.***.1 - ip of router
DNS: 127.0.0.1 - I have read conflicting information about the DNS settings!
On the client:
DNS: ***.***.***.51 - server's IP
My laptop is a named user in Active Directory. I have checked the domain name. I can ping the server, but can't ping the domain. I disable the firewall on the domain, just to test it and it hasn't made a difference.
Can anyone help me with this - I know there is probably a simple setting that I overlooked!!
Thanks in advance
05-15-2019 11:24 AM
I'd check 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. If problems persist please run;
05-15-2019 11:42 AM
Thanks for replying :)
I changed the DNS on the server to be its fixed IP address and the second DNS to point to 126.96.36.199. I then changed the second DNS on the client to be 188.8.131.52.
I then ran the DCDiag and got an error 81 saying the host **server could not be resolve to an IP address. Then it bugged out!
05-15-2019 11:54 AM - edited 05-15-2019 11:56 AM
Yes, that's not going to work. All domain members must use domain DNS exclusively. Members use domain DNS so they can find and logon to domain. Internet queries are passed along by default to root hint servers in a top-level-down fashion. You can optionally add public DNS addresses as forwarders.
(please don't forget to mark Best Response if helpful)
05-15-2019 12:00 PM
Sorry I misread what you said - should I remove the secondary DNS? I didn't have them in to start with.
05-15-2019 12:03 PM
Correct, 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. If problems persist please the mentioned files up on OneDrive.
05-15-2019 12:13 PM
I'd love to send you the files, but - I can't run DCDiag as it bugs out with an 81 error... :(
I've uploaded the server's ipconfig and the workstation's ipconfig and the repadmin.
Very much appreciate your help - thanks :)
05-15-2019 12:16 PM
Link to onedrive: https://onedrive.live.com/?id=root&cid=8A26BC6957547449
05-15-2019 12:16 PM
Sounds like you didn't run using the NetBIOS name of domain controller. You can find this by running;
05-15-2019 12:17 PM - edited 05-15-2019 12:26 PM
Library is empty (no files on OneDrive)
05-15-2019 12:28 PM
Okay maybe this is where I'm getting confused - my computer name is 2016server, my netbios name is 1405server? The domain I am trying to connect to is the netbios name no?
I moved the files into documents, so you should be able to see them now?
05-15-2019 12:31 PM
Still no files. Having two names for a domain controller may also be problematic.
05-15-2019 12:34 PM
Loaded DCDiag.log by using the computer name - it's in the documents with the other stuff :)
05-15-2019 12:36 PM
05-15-2019 12:45 PM
Yes, that worked. I only looked at the ipconfig /all 's There is an active IPv6 DHCP server on the network which must be configured correctly or the easier option (assume router) is to turn off IPv6 DHCP server in router.
If problems persist then put up a new set of files after changes.
05-15-2019 12:52 PM
05-15-2019 12:54 PM - edited 05-15-2019 01:14 PM
IPv6 DHCP assigned ip address, gateway and DNS
05-15-2019 01:34 PM
I've disabled IPv6 on the server, I can't login to my router to disable IPv6!
The diag is hanging on the server now....
05-15-2019 01:37 PMSolution
Also needs unchecked on any domain members.
05-15-2019 01:48 PM
YESSSSSS! I am a member of my domain! Whoo hoo!!
Fab! Thank you so much for all your help. :)
So all I need to now do is create a static IPv6 and Bob's your uncle.
Once again - thanks - I owe you a beer!