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

[blueice349]

Hi

I hope you can help.  I am trying to connect my windows 10 pro 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 tried everything I can think of to get this working any thought on what it could be? Maybe DNS issue or something is my thoughts

[#2]

I'd start by 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

[#3]

@Dave Patrick Can you lead me in the right direction? I am new to this domain stuff

[#4]

Please run;

• Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
• 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.

[#5]

@Dave Patrick So DC1 is domain controller 1 for ipconfig/all, but what is the DC2 for on the ipconfig/all?

[#6]

---

 So DC1 is domain controller 1 for ipconfig/all,

Yes, that's correct

---

but what is the DC2 for on the ipconfig/all?

a second domain controller if there is one

---

---

---

---

[#7]

@Dave Patrick I have a few files up and ready for you to look at, tho I need to run to the office for the problem computer. I will have 2 problem computers for you to look at as well. 
https://1drv.ms/u/s!Aqb4cbLzuCDubJlIyjM0z3bfaLE?e=vfccEh

[#8]

• A domain controller cannot have a DHCP assigned address, always needs static assignment.
• Assuming the static address is going to be 192.168.1.130 then it should have own address listed for DNS on connection properties along side loopback (127.0.0.1) and no others such as router or public DNS
• Also looks like there is an IPv6 DHCP server on network which will be problematic if not configured correctly. The simplest solution here is to disable the DHCP server (likely on a routing device at 192.168.1.254)

I didn't look at the other files since the above problems are show stoppers and need to be corrected to continue. After corrections if problems persist then put up a new set of files.

[#9]

@Dave Patrick I have made some changes and posted up the files for the DC and the two problemWorkstations. If you could check them out and let me know what your thoughts are on the issues. I have disabled the DHC on the 192.168.1.254 and on the DC

[#10]

• Domain controller is still DHCP assigned and also has router listed for DNS
• Problem workstations both have the router listed for DNS which isn't going to work.

The domain controller and problem member both must have the static ip address of DC listed for DNS and no others such as router or public DNS

[#11]

@Dave Patrick Can you lean me in the right direction to making these changes? I assumed I turned this off, but I am not 100% sure on what IP address and DNS to assign and where to

[#12]

@Dave Patrick 

[#13 · Accepted solution]

For example you can set them all statically like below

domain controller
address: 192.168.1.200
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200
DNS: 127.0.0.1

workstation 1
address: 192.168.1.201
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200

workstation 2
address: 192.168.1.202
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200

I've no idea if the above addresses are free to use but you can check them from cmd.exe then ping them. Then do ipconfig /flushdns, ipconfig /registerdns and restart netlogon service or simply reboot them. For a single DC setup be patient and wait 5 to 10 minutes for active directory / dns to fully start up.

[#14]

@Dave Patrick What if I have a laptop that comes and goes from the network and needs to login to another network wifi etc away from the org. How can I assign the IP and make sure it still works when they leave.

[#15]

You never did say if you got things to work? The simplest solution is to have the DHCP server hand out the correct address for DNS (in the examples above it would be 192.168.1.200) Then the laptop can use DHCP assigned.

[#16]

@Dave Patrick Okay so if I go and change the network adapter to the settings you gave me it then works as it should. Do I just need to now have the server set up to hand out the IP Addresses using DHCP? Will this also set the DNS like it needs to? and do I need to keep the DC set up on the network adapter?

[#17]

I'd focus on getting things working before adding complication like a new DHCP server if it were me. You can use the router also, you'll just need to change the DNS it hands out to the ip address of the domain controller.

 (please don't forget to mark helpful replies)