Have you run dcdiag with the /DNS switch from both DCs? (it's one of the options not run by default)
Client DNS config would also be high on the suspect list for me. Curious, what are the "some issues" you are having with the DC? From: Dave Vantine [mailto:[email protected]] Sent: Wednesday, November 17, 2010 12:51 PM To: NT System Admin Issues Subject: Domain Logon issues when a DC is down I have 2 DC's and on occasions when one goes off line for patching or some issue certain users are not able to logon to the domain and the messages indicate that there is no DC available. What it appears is that certain client machines are communicating with DC1 while other connect with DC2. I can actually reproduce this by running SET on a client machine to see which LOGONSERVER the machine is using then log out of the domain. If I shutdown that particular DC and then try to logon I will get the message that no logon servers available. I have run dcdiag and netdiag and there are no problems shown. I thought that the clients were suppose to be able to find all of the DC's available for logon purposes via the DNS srv records. As far as I know this has worked this way from the very begining of our Domain setup. I am having some issues with one of the DC's of late and may need to replace it so I would like to get this resolved. -- Thanks Dave Vantine ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
