Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Exchange loss of connectivity when Domain Controller Restarts..

Posted on 2007-04-03
8
Medium Priority
?
417 Views
Last Modified: 2010-03-17
We are running an Exchange 2003 server on a Windows 2003 server and are having the following problem:
Everytime we restart our domain controller we lose access to our mailboxes even though we have another DC locally and one out of state.  Our DC's also act as our internal DNS servers as well.  We are pretty much stumpped as to why this happens or how to remedy it.  Any help or nudge in the right direction would be greatly appreciated.

Thanks in advance,
Joe
0
Comment
Question by:techsfefcu
[X]
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
8 Comments
 
LVL 9

Expert Comment

by:robjeeves
ID: 18847447
G'day mate

Exchange needs a Global Catalog to funtion.  My guess would be the 2003 Server hosting Exchange isn't a GC.  So just checking you mean there is the 2003 with Exchange and another DC that gets rebooted and you loose your mailboxes? I'd suggest making the DC with Exchange a GC by following these instructions.  

http://support.microsoft.com/kb/313994

Also where does the 2003 point to for DNS? Itself?

Rob
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18847631
Exchange requires constant access to a domain controller. When that domain controller goes away, it does not fail over to another DC immediately. Exchange will not go looking for another DC for at least 30 minutes. During that time Exchange and Outlook is close to useless.

The fix? Don't reboot domain controllers during the day. I only reboot my domain controllers when I have to - I have just rebooted them in the last hour (it is gone midnight here) because of an update. Otherwise they are not rebooted.
The Exchange server was rebooted at the same time and the DC was up first, so when Exchange came online, its DCs were there.

Simon.
0
 

Author Comment

by:techsfefcu
ID: 18934490
Sembee,
I tried your recommendation and it didn't provided the results that I was looking for.  I have multiple GC's and multiple DC's.  I shut down the DC and waited for about 1 hour to see if Exchange would go looking for another DC and GC but, it didn't.  Not to mention that there has to be some kind of way for this to work.  I can't imagine that if my DC was FUBAR that we would lose all email capability. I guess that I'll just keep looking to see if there is a solution to this problem.
Thanks,

-Joe
0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 104

Expert Comment

by:Sembee
ID: 18935682
The solution is to restart the Exchange services.
I said it will not go looking for another DC for at least 35 minutes. That is the shortest time. It can take longer than that.
I would hope that in the event of a DC failure you would know about it and would take action.

Simon.
0
 

Author Comment

by:techsfefcu
ID: 18938493
OK...  I'm going to try restarting the Exchange services and se what happens..  

Thanks,

-Joe
0
 

Author Comment

by:techsfefcu
ID: 19052741
OK Here you go...  I can't take credit for this..  My Systems Administrator solved the problem with the loss of connectivity to Exchange via Outlook.  I am posting his resolution as he posted it in our knowledge base..  We worked this way for over a week without incident.

=========
1. We transfer FSMO roles to a new domain controller and set it as a GC.


2. Per the output of the policytest tool, the "Manage auditing and security log" permission for the Exchange Enterprise Servers group is missing from backup domain controllers. Without this permission, the two GC servers cannot be used by Outlook when primary domain controller is offline.


3. We run Setup/domainprep to fix the permission issue, which resolves our issue eventually. After shutting down the primary domain controller, outlook no longer loses connection with Exchange and use other domain controllers for directory and authentication services.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 21216362
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

609 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