maxrebo Posted October 9, 2014 Posted October 9, 2014 I'm trying to get to the bottom of our (slight ) problem with logon times and whilst checking our clients preferred DNS settings neither is configured (through DHCP) to point to our PDC (windows 2012) but instead is set to our other domain controllers (server 2008 r2) I was wondering what should I have my clients DNS settings pointing back to? Should it be the PDC as preferred DNS and either one of the 2008 boxes as secondary? Cheers
fairm010 Posted October 9, 2014 Posted October 9, 2014 I have 3 DC's here. I point clients to our PDC as primary and another DC as secondary. Works well.
ITGURU Posted October 9, 2014 Posted October 9, 2014 Is it definitely a DNS issue? Slow login can be caused by several other factors. Our DHCP is configured to publish all internal DNS Servers to the clients, and then Round Robin enabled on all servers for load balancing.
plexer Posted October 9, 2014 Posted October 9, 2014 The dns servers can be any/all of your available dns servers no need for it to be a specific box unless you think there is an issue with a specific server. Ben
ITGURU Posted October 9, 2014 Posted October 9, 2014 Just assign a PC a static IP and test with each DNS Server in the primary DNS. Could also try a flushdns just in case any issues. The dns servers can be any/all of your available dns servers no need for it to be a specific box unless you think there is an issue with a specific server. Ben
fairm010 Posted October 9, 2014 Posted October 9, 2014 As ITGURU said, slow logins could be anything from bloated roaming profiles to stuck login scripts. Provide some more details of how printers, mapped drives etc are deployed.
m25man Posted October 9, 2014 Posted October 9, 2014 I went to one today complaining about excessive login times... Client was suspecting and blaming this on a Network issue. Found a server and an access point sharing the same IP address, server had been assigned a static IP whilst the AP had the same IP assigned by DHCP reservation! This took all of 5 mins to detect and sort out with the Fluke kit. Network then had a clean bill of health, but still vslow logins... So then had a look through the first few Group Policies, never got past the "A's" and discovered one policy applying proxy settings that were made obsolete two ISPs ago, and one trying to install software from a server share decommissioned by the user 3 years ago! Left them sifting through the remaining 30 odd Group Policy Objects!! Interesting day....
ITGURU Posted October 9, 2014 Posted October 9, 2014 Thats one reason why I specifically have a DHCP Scope different to my static IP range so that never happens!
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