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.
A error occurred during connection/disconnection. Error code: 8511 [0 POP4 POP4 DOWN 6] (14)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
This can occur in various conditions. See ME300445, ME175354, ME232602, ME152897 and ME254818 links below.
As per Microsoft: "The OSI transport layer encountered an unexpected condition in communicating with the lower layer services. This usually indicates that a timing window closed during connection". See MSEX2K3DB for additional information about this event.
As per Microsoft: "This combination of errors usually indicates a misconfigured MTA and/or connector". See ME170471 and ME157630 to troubleshoot this issue.
When two Exchange Server computers are connected with an X.400 Connector, mail may queue up in both X.400 queues and not flow in either direction. The error occurs if the message transfer agent (MTA) becomes backed up while it is trying to deliver messages, and the transport connection is lost.
According to Microsoft: "This behavior can occur if you use Fully Qualified Domain Names (FQDN) or NetBIOS names to configure the connectors. To resolve this behavior, on both Exchange servers, configure the X.400 Connector to use the IP address of the remote MTA, and then restart both MTAs." See ME306959.
|Private comment: Subscribers only. See example of private comment|
|Links: ME152897, ME157630, ME170471, ME175354, ME232602, ME254818, ME300445, ME306959, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated