Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our network has suffered from years of neglect and improper configuration. I am finding that, using Wireshark, our LDAP operations are severely slowed and sometimes halted by it trying to connect to old DC's that have been relieved of DC duty a couple years ago but still exist keeping the same name and ip.

Any ideas on where to look/how to stop our network from apparently seeing those as DC's?

share|improve this question

migrated from Nov 2 '12 at 10:10

This question came from our site for professional and enthusiast programmers.

What kind of LDAP are you using, OpenLDAP, or does the DC here signify Active Directory? – sysadmin1138 Nov 4 '12 at 2:06

There is a knowledge base article from Microsoft:

If the LDAP Server doesn't read out the DCs from the AD itself, you will need to look into your LDAP Server configuration. (as you surely know)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.