Topic Last Modified: 2010-02-18

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	2006
Event Source	MSExchangeTransport
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport
Rule Name	The connection to the Send connector was disconnected by the remote server.

Explanation

This Warning event indicates that the specified Send connector was disconnected from the specified remote server. The disconnection was initiated by the remote server.

The disconnected session could be caused by a remote server problem or because an inbound connection limit has been reached on the remote server.

If the remote server has the Microsoft Exchange Server 2010 Hub Transport server role or Edge Transport server role installed, the disconnection could be caused when any of the following inbound connection limits are reached on the remote Receive connector:

ConnectionTimeOut
ConnectionInactivityTimeOut
MaxInboundConnection
MaxInboundConnectionPercentagePerSource
MaxInboundConnectionPerSource
MaxProtocolErrors

For more information, see Set-ReceiveConnector.

User Action

To resolve this warning, do one or more of the following:

Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.
Adjust the inbound connection limits on the remote server.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.