Why is it important for a DC to have only one NIC
Main Topics
Browse All TopicsI have and Exchange 2000 that crashes every Tuesday and Friday AM between 0500-0530. This all started 3 weeks ago when I updated all my servers to SP3 and Exchange to SP3 with the post SP3 Hotfix. Microsoft has been on the case for 2 weeks but thus far has not been able to solve it.
The crashes always seem to start with event 7031:
The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
And quickly move to:
2102
Process MAD.EXE (PID=1736). All Domain Controller Servers in use are not responding:
DC1.mydomain.com
dc2.mydomain.com
DC3.mydomain.com
After that I get a bunch of DCOM errors (Every 30 sec) because the information store is down.
There are no events on my DC's or other servers which indicate network connectivity issues at the time it goes down. I installed all security patches 3 weeks ago (including the one that fixes MS’s latest HOLE). I have also scanned the C:\ of the Exchange server for viruses. As a last note we have had no computers (knock on wood) that were affected by the MSBLAST worm so I don’t believe that has anything to do with it.
Any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Sorry for the delay:
For some services, (i.e. Exchange Server), the Microsoft Browser Service (a NetBios service) is used to determine network information (independent from any other statements of MS). The lack of the brwoser service is, that it can only bind to one single NIC at a time. Within a network, you have usually one Master Browser service, which is used to collect information an to support other machines. Whenever the browser services binds to a netcard outside your internal network, the browser service of other machines can not find this machine until the browser service binds back (as possible). Secondary, a DC usually (but need not) hosts the Master Brwoser service, which is then inaccessable, if the service binds to another card. You can determine this issue by "redirector" errors within your event log.
All these cases forces some malfunctions of other services within your network. They are usually temporary, but boring.
If you can not avoid a second NIC in your DC, disable NetBios over TCP/IP on this interface, if possible. This avoids that the browser service can bind to this NIC. As long as this interface is only for internet access, its not a problem. If this interface is a internal routing interface between to internal subnets, you will have a lot of temporary problems, if there is only one DC on one side of the network.
Business Accounts
Answer for Membership
by: BembiPosted on 2003-08-15 at 12:01:16ID: 9161892
Some ideas, some may be independend from each other.
- W2K Service Pack 4
- Check, if there is any other service, which will run between 5:00 and 5:30, i.e. Backup software
- have a look, when your online defragmenter runs (storage maintanance: tab "database" of the store properties")
be sure, that this service do not conflict with backup software or any others like virus scan.
- have a look at any anti virus software (i.e. Group Shield) and any sheduled task at this time
- check, if you hav any other issues, which will fall into your time scope (replication over dial-up / WAN connections)
As you get domain controller errors (All Domain Controller Servers in use are not responding):
Install the windows support tools from the CD oder better download the corresponding tools for the Servcie pack 3 from MS.
type browstat -status to see, where the master browser is located and maybe on which NIC the browser service is bound. If the master browser service is bound to an external NIC or ISDN card, exchange produces messages, that the domain controller can not be found. This is usually not a big problem, nevertheless is slows down the system and produces errors.
Be sure, that the browser servcie is bound to an internal NIC. The master browser service should be hosted on a domain controler (and a DC should allways have only one NIC!!). As the master browser server is able to float, it may be a good idea, to force the service to uise the DC and not any other machine. You can download the X_Setup from www.xteq.com (like Tweak_UI), there you have an otion to force a server to be the master browser or to deny a server to be it.
Another option to avoid the external binding of the browser service to disable NetBios over TCP/IP (configuration of TCP/IP - WINS on your netcard) for all external NICs. The browser service will only bind to NetBios enabled interfaces.
I've never seen, that the IS crashes when your DC errors arises, but I had other problems and a lot of errors (MAD.EXE and others) as well as DCOM errors, as long as we hadn't fixed the master browser issue.