Exchange Server 2003 Quits Responding  w/ Event ID 8250

Posted on 2005-03-16
Medium Priority
Last Modified: 2008-01-16
I have experienced this problem with our server for quite some time. The server is currently running W2K Server SP4 with Exchange 03 SP1. The Exchange 03 was an upgrade from Exchange 2000. This problem has persisited in both versions. I have every update and patch that I'm aware of installed. Spuratically, my server clients machines will loose their connection to Exchange for no apparent reason. When I physically go to the server, it appears that all is working normally. I can browse the network etc. and my resources are running in an acceptable limit. Once I reboot the server all is well once more and the clients can connect without any diffiuclty. My Exchange server isn't a DC. I'm not seeing any errors on my Active Directory to cause this. It as though the NIC card became uplugged but I'm on my second NIC that hasn't remedied the situation as I had hoped. The following errors occur while the strange behavior takes place. All I've read on the errors don't apply to my case.

Source: MSExchangeAL
Category: Service Control
Event ID: 8250
The Win32 API call 'DSGetDCNameW' returned error code (0x54b) The specified domain either does not exist or could not be contacted. The service could not be initialized. Make sure the operating system was installed properly.

Source: MSExchangeDSAccess
Category: Topology
Event ID: 2102
Process MAD.EXE (PID=2896). All Domain Controller Servers are not responding.
Question by:Danstr1
1 Comment
LVL 104

Accepted Solution

Sembee earned 750 total points
ID: 13560108
If the problem existed in the previous install then upgrading the Exchange version would have only caused further difficulties. I don't upgrade anything on a server - certainly not Exchange. The data is swung out to another machine so that original can be rebuilt. You get a server that is a lot happier that way.

Both messages basically boil down to the same problem - the server is having difficulties communicating with the domain.

Standard check first.
The server should be pointing to domain controllers ONLY for DNS. Furthermore at least one of those DCs must also be a global catalog. There should be no external DNS servers in the core server network configuration.

I would install the support tools from the Windows 2000 CD-ROM and use those to test the domain connectivity. When the system has failed, repeat the tests before you reboot. I know that users will be screaming at you to get email back, but make them wait as you need to run the tests while the server is down to see whether the results are different.


Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

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

Let us take a look at the scenario, you have a database that is corrupt and you run the ESEUTIL command only to find you are unable to repair it. How do you now get the data back?
Disk errors can be the source of sundry problems for the Exchange server, the most common one being that the database fails to mount.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
In this video I will demonstrate how to set up Nine, which I now consider the best alternative email app to Touchdown.

601 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