Forum Discussion
Windows Server 2016 No Internet Access after AD, DNS and DHCP setup
In the DCDiag file there is are multiple errors regarding no response from DNS server. Is there anything helpful in that?
If you can put up the unedited files yes there would be. There's no risk in posting the private (non routable) addresses. Need to have the whole picture.
The unedited DCDiag files can be acessed here:
https://sncoptiramp-my.sharepoint.com/:f:/g/personal/upathak_optiramp_com/EpterLubTppEkYir_tAvE6IBLrEmzpQopuDBJDLsk2FBMw?e=MjYi16
I am guessing this is an old Blog:
there are several questions to be asked: are you running VM on Hyper-V what are your Hyper-v switch settings ? are you on the same subnet as your Edge router ? also check your DNS settings ? Subnet mask. is DHCP enabled ? there are bunch of things that could block your internet connectivity. here what I would do either configure a proxy on an authorized server not client, enable DNSSEC and Flooding guard on your AD Server, import the proxy settings from IE using NETSH.
so if your AD Server does not have a global DNS zone it will not handle any Internet requests including your own AD server requests. once you add a global zone to the AD Server itself it will expose your server to the global network.
Sounds good. Please also include the ipconfig /all from a DHCP assigned domain member.
- Yes i did make those changes and still no luck. I will upload the files and send the link.
Did you fix the issues I suggested? If so put up a new set files and I'll have a look.
- Hi Dave,
I can provide you the client DCDiag but my main issue is DNS server setup for Windows Server 2016. Are there any particular steps to troubleshoot or fix this or reinstall DNS server with step wise checks? On the DC please add server's own address (192.168.124.166) to connection properties DNS. Client file appears identical to that of DC (should have been run on problem client?). I'd suspect a circular reference but can't tell without seeing the problem client ipconfig /all DHCP result. I'd remove the router as forwarder and if necessary use ISP's public DNS or use google DNS (8.8.8.8, 8.8.4.4) Similar below;
