Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 9176 Source: MSExchangeSA

NSPI Proxy can contact Global Catalog <host name> but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot <host name> as soon as possible.
As per Microsoft: "This event indicates that the Exchange server was able to contact a server that is designated to be a global catalog server but did not get a response from the Name Service Provider Interface (NSPI) on that global catalog. This can occur because the NSPI is not advertised by the global catalog server, possibly because the server was made a global catalog and was not restarted". See MSEX2K3DB and ME883728 for information about this event.
This issue may occur if you promoted a domain controller to a global catalog server, and you did not restart the new global catalog server. New MAPI client computers cannot connect to Exchange 2000 if you do not restart the new global catalog server after you promote the domain controller. See ME317338 for more details.

As per ME811173 to work around this behavior, use fewer Global Address Book views or add more (and more powerful) global catalogs.

Also check ME285137 and ME305596 to fix your problem.
This event is caused by the Name Service Provider Interface (NSPI) is not advertised by the global catalog server. Rebooting the server will not correct the issue. Windows 2000 SP3 is suppose to fix the problem, but does not. The workaround is to demote the Domain Controller from GC server status, restart the GCS, then promote the DC to a Global Catalog server again. See ME280401.  
Microsoft suggests ME304403 - Exchange Considerations for Promoting a Domain Controller to a Global Catalog Server and ME321318 - The Top Exchange 2000 Directory Service Support Issues.
Every GC in the Forest posted the same error to Exchange system log. Caused by a reboot of the DC that contains Enterprise Configuration for Recipient Update Service. Do nothing. Works fine after reboot.

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

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.