We have six AD Windows servers (I believe they are all 2008 R2, running at a functional 2008 R2 domain)
All six servers have the AD role and DNS role. We have about 1200 workstations in our environment and we have been experiencing extremely slow intermittent logins for a handful of workstations(mostly older machines). When we had this issue, the GPO had 'always wait for the network at computer startup and logon' enabled. It was decided to disable the setting. We now have users reporting issues with their logon scripts not running and/or not connecting to the domain. It's like they are logging into a temp account, because their NIC does not initialize before it tries to contact the domain (this mostly occurs with the faster workstations).
I was thinking their may be an issue with the DNS servers, I ran the command dcdiag /test:DNS /e /v >dnsTest.txt and noticed a lot of incorrectly configured NIC settings for the servers preferred/secondary DNS settings. Please see image below for overview. I included what I think the proper change should be (also in image)
DC5 has it's preferred DNS set to a random workstation, secondary is another random workstation, and third is a random server, and fourth is back to itself.
I'm not a Windows Admin, but I'm trying to research the issue because we are getting no where.
TLDR : Can incorrectly configured NIC settings on the DNS server cause issues to the users bootup times? Or what issues would these incorrect settings cause?
No comments:
Post a Comment