Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2897
  • Last Modified:

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

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:

get-ExchangeServer
Failed
Error:
Could not find any Domain Controller in domain (mydomain).local.

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





get-UMServer
Failed
Error:
Could not find any Domain Controller in domain (mydomain).local.

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




--------------------------------------------------------
OK
--------------------------------------------------------

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.
0
dustinwk
Asked:
dustinwk
  • 2
1 Solution
 
DenverRickCommented:
Sounds like a DNS problem.  Test with:

ping domain.local

ping DCx   (Domain Controller)

ping dcx.domain.local

All three must resolve and work.
0
 
dustinwkAuthor Commented:
I pinged from the exchange server and all three resolve to the primary domain controller
0
 
dustinwkAuthor Commented:
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!
0
 
ex-rockerCommented:
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)
In-site:
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
 Out-of-site:

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

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now