tekguru 0 Posted October 9, 2013 Share Posted October 9, 2013 The DNS on the server is affecting the clients forcing them to go through the server (which does not always work). Is it safe to fix it by removing the DNS role on the server? Link to post Share on other sites
adster01 0 Posted October 9, 2013 Share Posted October 9, 2013 Simple fix is to disable the Windows server LAN configuration service on all client computers. Link to post Share on other sites
tekguru 0 Posted October 9, 2013 Author Share Posted October 9, 2013 Yep I know that one. But for some reason that service is not even present - and I've looked twice so far (each time after rebooting)! Weirdness. For the moment I'd set the DNS forwarders on the server to Google and that seems to be working so far for resolution. Link to post Share on other sites
jmwills 284 Posted October 9, 2013 Share Posted October 9, 2013 This blog would be worth your time reading: http://blog.mpecsinc.ca/search?q=DNS Link to post Share on other sites
tekguru 0 Posted October 9, 2013 Author Share Posted October 9, 2013 That does look useful, I'll read through in depth over the weekend! Link to post Share on other sites
ikon 439 Posted October 12, 2013 Share Posted October 12, 2013 This blog would be worth your time reading: http://blog.mpecsinc.ca/search?q=DNS "Repeat After Me: DHCP and DNS Belong on a DC" LOL, a man after our own hearts Link to post Share on other sites
jmwills 284 Posted October 12, 2013 Share Posted October 12, 2013 I think if someone does a tracert to a site via both methods, they will see what Philip is talking about. Link to post Share on other sites
tinkererguy 22 Posted December 11, 2013 Share Posted December 11, 2013 Yep I know that one. But for some reason that service is not even present - and I've looked twice so far (each time after rebooting)! Weirdness. For the moment I'd set the DNS forwarders on the server to Google and that seems to be working so far for resolution. That is one method that folks have reported seems to work nicely. I've figured out an alternative method tonight, where DNS can be left as DHCP fed, avoiding the nuisance of any manual DNS tweaking of all your NICs (VMware, Hamachi, VPNs, etc), detailed here: TinkerTry.com/how-to-make-windows-server-2012-r2-essentials-client-connector-install-behave-just-like-windows-home-server aka, Connect to Windows Server 2012 R2 Essentials without affecting your DNS, staying in workgroup mode Link to post Share on other sites
tekguru 0 Posted December 11, 2013 Author Share Posted December 11, 2013 Yes! Completely awesome Paul, now in place and hopefully life will remain a lot easier now! My thanks! Link to post Share on other sites
tinkererguy 22 Posted December 11, 2013 Share Posted December 11, 2013 Time will tell! But yeah, tweaking the registry seems more likely to "stick" through the expected Update Rollups, at least more likely than my (more-hack-like) tweak of the past, the stopping of that "Windows Server LAN Configuration" that had to be redone after each Update Rollup, also requiring DNS get manually cleaned up too (I have 14 machines, each with between 2 to 7 NICs to clean. Argh!). See also new thread I just started in the R2 area: http://homeservershow.com/forums/index.php?/topic/6712-connect-to-windows-server-2012-r2-essentials-without-affecting-your-dns-staying-in-workgroup-mode/#entry73414 Link to post Share on other sites
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now