Forum Discussion
Windows 10 Pro can't see active directory domain on Windows Server 2016
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.1workstation 1
address: 192.168.1.201
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200workstation 2
address: 192.168.1.202
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200I'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.
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
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
- 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.
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
- 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