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.
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.
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?
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)
