Exchange Server 2003 Quits Responding w/ Event ID 8250
Posted on 2005-03-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.
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.
Event ID: 2102
Process MAD.EXE (PID=2896). All Domain Controller Servers are not responding.