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

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

Why do users lose exchange connectivity when I reboot one of my domain controllers?


I've got a 2000 domain controller, and two 2003 domain controllers (one which runs exchange 2003).  Users have windows 2000 professional and outlook 2003.  When I reboot the 2000 domain controller, everyone loses exchange connectivity.  I found these two errors on the exchange servers error log:

this error occurs numerous times all at once:

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      RFR Interface
Event ID:      9074
Date:            5/6/2005
Time:            9:44:48 AM
User:            N/A
Computer:      EXCHANGE
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].

For more information, click http://www.microsoft.com/contentredirect.asp.

Then, the second error occurs once:

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2103
Date:            5/6/2005
Time:            9:33:46 AM
User:            N/A
Computer:      EXCHANGE
Process MAD.EXE (PID=1436). All Global Catalog Servers in use are not responding:

For more information, click http://www.microsoft.com/contentredirect.asp.

The server that is referred to above is the one I rebooted.

The windows 2003 server that does not run exchange (its a file and app server) is the operations master.  I believe that all three domain controllers are global catalog servers so i don't know it says ALL global catalog servers in use are not responding.

I have read the MS articles related to the errors and followed all the steps and found nothing (ran policytest.exe, checked replication,etc etc)

Before I write a book, I'll end here.  Feel free to ask more details about my tcp/ip configs, etc or more on what i've tried.


PS-Should I post this in networking instead or as well?
David Scott, MCSE
David Scott, MCSE
1 Solution
Upon first thought I would say that your Exchange server is pointing to the rebooted server as the DC and GC.
Although it may after a period of time start searching for a new DC/GC. I am not sure how long it will wait before it does this or how to change the time interval.

Hopefully someone else will add their ideas.
David Scott, MCSENetwork AdministratorAuthor Commented:
i think i found it.  turns out that the 2000 server was the only global catalog server in the domain.  I made both the 2003 servers global catalogs.  I am going to reboot the 2000 server again and see what happens


Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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