As per Microsoft: "This event is displayed in the application log when the Exchange server is unable to access a domain controller. For example, this event can occur when a domain controller is restarted, if that is the ONLY domain controller in the site to which the Exchange server belongs". See MSEX2K3DB for more details on this event.
See ME842116 and ME895858 for additional information on this event.
1. Right click on My Network Places and select Properties
2. From the Menu Select Advanced and then select the Advanced Settings
3. In the connections box confirm that the Internal Network Card is at the top of the binding order. Select OK
4. Right click on the External NIC and select Properties
5. Highlight Internet Protocol (TCP/IP) and click on the Properties button. Then click on the the Advanced button
6. On the Advanced TCP/IP Settings select the DNS Tab.
7. Remove the ISP's Ip address from DNS and leave it blank.
8. Click OK to save the Network settings.
9. Verify that the Internal network card is configured to only point to the SBS server's internal IP address for DNS using steps 4 - 8.
10. Go to Start/Programs/Administrative Tools/DNS
11. Right click on the server's name in the DNS MMC and select Properties
12. Click on the Forwarders tab. Verify that Enable forwarders is selected and that the DNS server address for the ISP are listed
13. Click OK to exit the dialog
14. Reboot the server.
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.