Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2014-10-15
6
Medium Priority
?
337 Views
Last Modified: 2014-10-23
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!
0
Comment
Question by:xcomiii
[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
6 Comments
 
LVL 35

Accepted Solution

by:
Seth Simmons earned 2000 total points
ID: 40383462
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
0
 
LVL 23

Expert Comment

by:Thomas Grassi
ID: 40383466
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
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40389491
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.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
LVL 9

Author Comment

by:xcomiii
ID: 40390067
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.
0
 
LVL 9

Author Comment

by:xcomiii
ID: 40390467
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
0
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 40390468
i stated in the beginning to reboot the exchange server
0

Featured Post

Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Question has a verified solution.

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

This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

722 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