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. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
NSPI Proxy encountered an error while receiving a packet. The target Domain Controller or the network or a client might be down. The winsock subsystem returned the error:[<error code>]. The circuit that received this error is being closed.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange System Attendant (MSExchangeSA) service?
What is NSPI?
Peter Van Gils
This event is logged when you're running Exchange Server 2007 and HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\MaxUserPort is set lower than 60000. ExBPA will recommend keeping this on the default 60000. See “MaxUserPort Key is Missing or Non-default” for additional information on this issue.
This event is logged whenever a Collaboration Data Objects (CDO) script that opens a MAPI session runs on the server that is running Exchange Server 2003 SP1. See ME912062 for additional information about this event.
As per Microsoft: "This event indicates that the NSPI interface of the Exchange server encountered a problem when communicating with a global catalog server. This problem may be a transient one. However, if this event is logged repeatedly, then further investigation would be needed". See MSEX2K3DB for details on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: ME912062, MaxUserPort Key is Missing or Non-default, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated