Network Outbound Packets beyond threshold
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2006-02-13
The Microsoft® Exchange Server Analyzer Tool includes a performance data collection engine that is used to query performance counter objects. The performance data collection engine collects data from the Packet Outbound errors performance counter of the Network Interface performance object to analyze performance data.
The Packet Outbound errors performance counter indicates the number of outgoing packets that could not be transmitted because of error. The value of the Packet Outbound errors performance counter should be zero. If the Exchange Server Analyzer determines that the Packet Outbound errors performance counter has a value greater then zero, the Exchange Server Analyzer displays an error.
This error usually indicates that the server is experiencing periods of unresponsiveness, causing mail flow to slow down or stop. Additionally, Microsoft Outlook® clients who connect to this server may receive the RPC cancel Request dialog box.
This error is most likely caused by a faulty or damaged network interface card (NIC).
To resolve this error, you must determine the cause of the outgoing packet errors, and then correct the problem. If the outgoing packet errors are caused by a faulty NIC, replace the card immediately.
Consider the best practices in the following articles:
For information about network bandwidth considerations, see Network Performance in "Understanding Exchange Performance" in the Performance and Scalability Guide for Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=47576).
For information about troubleshooting network problems, see "Ruling Out Network-Bound Problems" in Troubleshooting Microsoft Exchange Server 2003 Performance (http://go.microsoft.com/fwlink/?LinkId=47588).