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: 492
  • Last Modified:

Exchange seerver

Hi,

Our domain controller crashed yesterday and I managed to get it back up and running again. Unfortuantely when I try to log on to the exchange server is I get a message Windows cannot connect to the domain, either the domain controller is down or other unavailable........Some users can logon to their PCs with no issues and receive emails while others can not. When I ping the exchange server I get a response.

We use server 2003

Any ideas!
0
PlanAndSimple
Asked:
PlanAndSimple
  • 9
  • 5
  • 3
  • +5
3 Solutions
 
Dave_ANDCommented:
Make sure there is a computer account in AD for the exchange server, and check DNS is up and running on the DC. Can you login in to the exchange server as the local domain account and check the network settings, and ping some NETBIOS names?
0
 
Mike ThomasConsultantCommented:
Try simply restarting the exchange server.
0
 
elbereth21Commented:
Before restarting the exchange server (which is a good suggestion), try restarting net logon service on the DC.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
BusbarSolutions ArchitectCommented:
make sure that the computer account of the Exchange server is in AD and that trust is correct and DNS is working correctly, it might be necessary to run /preparead again.

also try from the Exchange sever to dis-join and it a join it to the domain (don't restart after disjoin
0
 
PlanAndSimpleAuthor Commented:
Hi,

There is an account for the mail server, DNS is up and running. I have logoned on locally to the servers and an getting the follwoing errors in event viewer.

Event 4: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/coumail.gcc.int.  The target name used was GCC\COUMAIL$. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (GCC.INT), and the client realm.   Please contact your system administrator.

Event 9188: Microsoft Exchange System Attendant failed to read the membership of group 'cn=Exchange Domain Servers,cn=Users,dc=gcc,dc=int'. Error code '8007203b'.

Please check whether the local computer is a member of the group. If it is not, stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services.

eVENT 2114: Process MAD.EXE (PID=3324). Topology Discovery failed, error 0x80040952.

Thanks for your help


0
 
PlanAndSimpleAuthor Commented:
Also I'm able to ping all other servers on the network from the mail server.
0
 
MinoDCCommented:
Login to Exchange with local Administrator.

In Computer properties, in Name Tab, delete ONLY domain extension (eg.: domain.com , you delete only .com ) and click OK .

Insert Domain Administrator Password and restart Exchange.

Next reboot , login with domain admin account.
0
 
PlanAndSimpleAuthor Commented:
Just in the process of rebooting mail server, will let you know the outcome.
0
 
PlanAndSimpleAuthor Commented:
System rebooted with same problem.

MinoDC not sure I follow. Ours in a .int domain, if I delete the .int from the domain tab will this not remove from/or not id domain next time I logon on after reboot?
0
 
MinoDCCommented:
If you delete the extension from domain tab (.int), Exchange rewrite its SID in domain and Re-Trust the domain.
0
 
MinoDCCommented:
ah...Exchange ISN'T remove from domain in this way and the domain extension , after reboot , is rewrite in domain tab .
0
 
PlanAndSimpleAuthor Commented:
Hi, tried it and it let me log on as network admin but after reboot of PCs still cannot access emails. Outlook not connecting to sever.
0
 
MinoDCCommented:
View if all exchange service and db are OK.

Next Close and re-open outlook client .

which version of exchange and outlook you have ?
0
 
PlanAndSimpleAuthor Commented:
Hi,

In services the Microsoft Exchange  Info store won't start error; dependcy service or group failed to start.

Exchange 2003 and outlook 2003.
0
 
MinoDCCommented:
what error you have in the event viewer
0
 
PlanAndSimpleAuthor Commented:
Error under Apps = MS ExchangeDSAccess Error ID 2114: process INETINFO.EXE (PID=1364). Topology Discovery failed, error 0x80040952.

Error under Sys = Service Control Manager Error ID 7001:  The Microsoft Exchange Information Store service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The operation completed successfully.

0
 
PlanAndSimpleAuthor Commented:
Hi, got services backup and running but still have problems with a users not being able to access emails.
0
 
sunnyc7Commented:
do you have any other DC in the domain - or was this the only DC

You can sit and troubleshoot your way out of all kerberos / gpt and other errors.
OR
you can run dcpromo on your domain controller.
Reboot that.
then reboot exchange

and hope exchange gets it.
0
 
TechHammerCommented:
On a side note.  After  you resolve your initial issue, add DC services to a backup server for failover purposes.
0
 
sunnyc7Commented:
Very important point by @techhammer

Please post back if you have any questions.
0
 
PlanAndSimpleAuthor Commented:
Thanks for all your help all services backup and running followed sunnyc7 and MinDC instructions and everything logging on again!

9 year old servers but got funding through yesterday to upgrade hardware and software after pushing for it for over a year...always the way!

Thanks Again!
0
 
sunnyc7Commented:
Glad it worked out.
Thanks for the points.
0

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.

  • 9
  • 5
  • 3
  • +5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now