Hi,
We are very new to Windows server (as you can probably tell by reading this!) and are having a few issues with DHCP, DNS and the domain.
We have a BT business router on 192.168.0.1
Windows Server Essentials 2012 R2 on 192.168.0.2
Can someone tell me what settings we should have on the client NIC's and Sever NIC if we want the router to continue doing DHCP, but the Server to be the domain controller. We currently have the clients setup to auto on everything. The server NIC set to static IP of 192.168.0.2 and the Default gateway and primary DNS set to 192.168.0.1 (the BT router).
This works OK, but we are having 2 issues:
Some clients (not all) have their primary DNS reset to 192.168.0.2 on restart (presumably the server lan service installed by the connector software is doing this) and they get very slow internet or none at all.
Also some clients are having issues logging in and will get a blank desktop and a popup asking for windows credentials again or sometimes the login box with error message 'The system cannot contact a domain controller to service the authentication request. Please try again later'. We did try running the DHCP role on the server but were having similar issues.
What are the ideal settings we need for our setup? Are there any disadvantages of continuing to use the router for DHCP?
Many thanks!