Forum Discussion
Windows 10 can't see active directory domain on Windows Server 2016
- May 15, 2019
Also needs unchecked on any domain members.
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;
- Dcdiag /v /c /d /e /s:DCName >c:\dcdiag.log
(please replace DCName with your domain controller's netbios name) - repadmin /showrepl >C:\repl.txt
- ipconfig /all > C:\dc1.txt
- ipconfig /all > C:\dc2.txt
- ipconfig /all > C:\problemworkstation.txt
then put unzipped text files up on OneDrive and share a link.
- Bill1505May 15, 2019Copper Contributor
Thanks for replying :)
I changed the DNS on the server to be its fixed IP address and the second DNS to point to 8.8.8.8. I then changed the second DNS on the client to be 8.8.8.8.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!
- Dave PatrickMay 15, 2019MVP
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)
- Bill1505May 15, 2019Copper Contributor
Sorry I misread what you said - should I remove the secondary DNS? I didn't have them in to start with.