Exchange 2007 (Could not find any Domain Controller in domain)

Posted on 2008-10-20
Last Modified: 2012-05-05
I recently had a power outage and some of my servers shutdown improperly. Now when I try to open up the Exchange Management Console, I get the following errors.

Microsoft Exchange Error
The following error(s) were reported while loading topology information:

Could not find any Domain Controller in domain (mydomain).local.

Domain controller not found in the domain "(mydomain).local".

Could not find any Domain Controller in domain (mydomain).local.

Domain controller not found in the domain "(mydomain).local".


I am still able to send and receive mail. Everything seems to be working but I cannot manage my Mail server. I can ping the primary and secondary domain controller so I am not sure what the issue is here.
Question by:dustinwk
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2

Accepted Solution

DenverRick earned 500 total points
ID: 22759656
Sounds like a DNS problem.  Test with:

ping domain.local

ping DCx   (Domain Controller)

ping dcx.domain.local

All three must resolve and work.

Author Comment

ID: 22759696
I pinged from the exchange server and all three resolve to the primary domain controller

Author Closing Comment

ID: 31507890
Huh thats weird. I have been messing with this all morning. I first rebooted the server. No luck there. Then I flushed the DNS cache on the exchange server. Still no luck. Then I pinged all three items like you said from the exchange server. All worked. Now I can use the EMC and there are no erros.

Any ideas on why this fixed the issue? Don't get me wrong I'm glad it is fixed but I would love to know what happened and why this helped.

At any rate this somehow fixed my issue even though this was only a troubleshooting step so thanks!

Expert Comment

ID: 35358416
I'm running into this same error. All 3 DCs ping just fine, and just 12 minutes ago our application log displayed this:

Process STORE.EXE (PID=3916). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
server1.domain.local      CDG 1 7 7 1 0 1 1 7 1
server2.domain.local      CDG 1 7 7 1 0 1 1 7 1
server3.domain.local      CDG 1 7 7 1 0 1 1 7 1

All server and domain names have been changed to protect the innocent :-)

Featured Post

Major Incident Management Communications

Major incidents and IT service outages cost companies millions. Often the solution to minimizing damage is automated communication. Find out more in our Major Incident Management Communications infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question