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

Exchange 2003 won't start after shutdown of a domain controller

I shutdown an old Win2003 R2 Domain Controller, and now the only Exchange 2003 server in the domain won't start. To be exact, the Exchange System Attendant will not start.

What bothers me, is that I still have 3 other DC's that works fine, 1 old Win2003R2 DC in the same subnet and 2 new Win2008 R2 DC's in another subnet (same internal network).

And of course, the eventlog is always starting with eventid 5719 after a reboot,
"This computer was not able to set up a secure session with a domain controller in domain DIAKONSYK due to the following:
There are currently no logon servers available to service the logon request.  
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  "

Googling eventid 5719 gives me information not relevant in my case, since there are other DC's that should handle the traffic from the Exchange server. I also have checked the settings for "manage remote logs" in Default Domain controllers policy, it shows as it should be.

And yes, the DNS settings on the nic points to the new Win2008 r2 DC's.

Anyone with ideas? Thanks!
1 Solution
Seth SimmonsSr. Systems AdministratorCommented:
in the server properties of EMC, there is a directory access tab where you can manually specify servers - i would check first to make sure nothing was manually changed to use only a specific domain controller.  if that looks good, just reboot the exchange server
Thomas GrassiSystems AdministratorCommented:
Did you leave the 2003 Dc down?

Are the other 3 DC set as a global catalog?

Exchange needs to find the global catalog to work properly

Check the event log for event id 2080  in the application log of the exchange server
Gareth GudgerCommented:
trgrass is correct. You need to make sure you have a Global Catalog available. Not just a DC. Also, the server you shut down didn't contain all your FSMO roles did it? These are safely running on another DC right? Just want to make sure.

To check run NETDOM /QUERY FSMO from a command line.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

xcomiiiAuthor Commented:
Thanks for all replies.
There are 3 others GC's, so that was not the problem.

The problem was that the Exchange Console GUI was freezing each time I was going to change Domain Controller, but I managed at last, guess the server is pretty unstable by itself.  Rebooted and everything works finally.
xcomiiiAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for xcomiii's comment #a40390067

for the following reason:

Found out my self
Seth SimmonsSr. Systems AdministratorCommented:
i stated in the beginning to reboot the exchange server
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

7 new features that'll make your work life better

It’s our mission to create a product that solves the huge challenges you face at work every day. In case you missed it, here are 7 delightful things we've added recently to monday to make it even more awesome.

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