Recent Posts

Monday, September 4, 2017

Configure Client Server in Domain Network connecting to router internet connection (Fix all DNS issues)

Known Issues while configuring the Domain in windows 2012 r2 and Setting up Client Computer and to make internet working:


  1. After installing Active directory , Domain Controller , DHCP in windows 2012 r2 there was issue connecting client computer to the domain – the client couldn't find the domain 
    • Solution : Change the Preferred DNS of client to Server IP and Connect to Domain
    • But now there is no internet in the client because Server DNS and Router DNS are two different things
    • To fix internet in Client – only option was to remove server ip from DNS settings in client and it will ultimately route to router and internet will work.
      • But again there is problem with the client. Since the DNS of serve r is not Known and it will be looking into Public DNS for its internal Domain, the initial log in of the client computers were taking ages to log in (more than 10 mins for some
  2. After configuring Mikrotik Router both have DHCP running and the laptops running under wi-fi were distributed different IP by router and in Lan computers ip was distributed through Windows Server 2012 DHCP 
    • Problem was there were number of times ip-conflict scenario was appearing.


To Fix all this issues after many blog posts and trial and errors, I have come up with the permanent fix. 

Server Setup – (Windows 2012 R2 Server)

  1. Install Windows 2012 R2 Server – Active Directory, Domain Controllers, DHCP 
  2. Give server IP address – In my case it was 192.168.1.160 (say)  - So your DNS, DHCP and AD has same ip in the Server
  3. In Server adapter :
    • Ip Address will be : 192.168.1.160
    • Subnet Mask auto populate
    • Default Gateway will be your router Address in my case it is (192.168.1.1)
    • Preferred DNS same as own IP address: 192.168.1.160
    • Alternate DNS : Keep public IP in case your server couldn't resolve some DNS names : 8.8.8.8
    • Now Internet should be working in your Server, if not then check your router unless the internet is working on server don’t proceed 


Client Setup - (Windows 7)

  1. I am connecting to server using Windows 7
  2. Since if you don't put the ip of the Server in DNS of client it may not find your domain 
  3. So first open Network and sharing
  4. Change Adapter Settings
  5. Enter Preferred DNS Server as Server IP –192.168.1.160
  6. Go to Computer- Properties -Change Settings 
  7. To rename this computer or change the domain - click Change
  8. Enter fully qualified domain name (FQDN) on the domain and click ok
  9. The computer will join the domain – Restart the computer 
  10. Now Client Adapter settings look simple no complications 
Now Check Internet and mapped drives in your Client computer

  1. Mapped drives should work 
  2. Internet Not working
    • Now In this case your client PC is configured to point to your local DNS server (192.168.1.160) 
    • It has reached the server but it couldn't forward request to public DNS so it is stuck there and thus no internet
    • To Forward DNS you need to change small setting in your Server
Windows 2012 R2 Server – Forward DNS to make internet working in client computer

  • Go to Server Manager
  • Select DNS
  • Right click the DNS IP and open DNS Manager
  • Right click the server and click Properties
  • Check Interfaces tab which should only listen to your server IP address – 192.168.1.160

  • Now Click on Forwarders – Here you might see 192.168.1.1 that is incorrect , it must forward your requests to either your ISP DNS address or public domain then only your client can resolve the domain and thus internet works.
  • Delete the 192.168.1.1 entry which is not resolving anything
  • Enter DNS provided by your ISP or just enter public IP (8.8.8.8) it doesn't matter if both are present (settings pic below)
  • Now Press ok and check your client – internet must be flowing in …. Happy chappy

Related Posts by Categories