Forum Discussion

Bill1505's avatar
Bill1505
Copper Contributor
May 15, 2019

Windows 10 can't see active directory domain on Windows Server 2016

Hi all

 

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:
DNS Client
FDRP
SSDP Discovery
UPnP Device

On the server:
IP4:  ***.***.***.51

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:
IP4: ***.***.***.07

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

Active Directory
Windows Server
  • Dave Patrick's avatar
    Dave Patrick
    MVP
    May 15, 2019

    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.
     
     
     
    • Bill1505's avatar
      Bill1505
      Copper Contributor
      May 15, 2019

      Dave Patrick 

       

      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 Patrick's avatar
        Dave Patrick
        MVP
        May 15, 2019

        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)

         

          

         

         

         

         

Resources