Ad Authentication issues

hi guy's

small issue have here, every 7days domain controllers (server 2008r2) give on me , not authenticate users on domain. when opening aduc following error:

"naming information cannot loacted following reason: server not operational

if trying connect domain controller running windows 200, verify windows 2000 server service pack 3 or later installed on dc, or use windows 2000 administration tools.  more information connecting dc's running 2000, see , support"

when try run dcdiag on faulty server following:

"directory server diagnosis

performing inital setup:

trying find home server...

home server = <servername>

ldap search capability attribute search failed on server <servername>, return value = 81"

the server can ping other dc , can pinged other dc.  can resolve ip name.

i have checked numerous site , of issues have seen point 2003 server.  have disabled of av on servers , when have ran dnslint following:

"c:\atos\dnslint>dnslint /ad /s localhost

 

dnslint attempt verify the

dns entries used in ad replication

 

using 127.0.0.1 ldap

dnslint check if local system can

resolve cname , glue (a) records

used active directory forest replication

using locally configured dns server(s)

 

this process may take several minutes complete.........

ldap query speficied ldap server on tcp port 389 failed

server down

 

ldap query speficied ldap server on tcp port 389 failed

ldap server specified appears down

 

specify different ldap server , run command again"

but can telnet server on port 389.

this happens on both physical , virtual dc, once reboot problem server works fine 7 days happens again.

any thoughts appreciated.

cheers

you welcome, far! between paul, myself , others respond, we'll our best bottom of this.

one thing stands out red flag dc multihomed. understand 1 of them management interface possibly used vm team manage, backup, etc, point multihoming dc problematic. can read on nuances in blog. i'll re-writing blog clear things in it, basis dns registrations multiple interfaces, can cause issues clients resolving dc interface not have route to. i'm leaning towards config being culprit. can modify reg stop management interface registering dns.

multihomed dcs (with more 1 unteamed nic or multiple ips) dns, rras, iscsi, clustering interfaces, management interfaces, backup interfaces, and/or pppoe adapters - multihomed dc not recommended configuration, there ways configure dc registry mods:
http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

active directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294/

---

ace fekay
mvp, mct, mcitp/ea, mcts windows 2008/r2 & exchange 2007, exchange 2010 ea, mcse & mcsa 2003/2000, mcsa messaging 2003
microsoft certified trainer
microsoft mvp - directory services
technical blogs & videos: http://www.delawarecountycomputerconsulting.com/

this post provided as-is no warranties or guarantees , confers no rights.

Windows Server  >  Directory Services