11001

Buffer Too Small

This error is unlikely because the Exchange Server Analyzer generates a standard request.

11002

Destination Net Unreachable

Request failed because the network that contains the destination computer is not reachable. No valid route exists to the destination computer.

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11003

Destination Host Unreachable

Request failed because the destination computer is not reachable.

For more information, see Active Directory server down or unreachable.

Alternatively, this error may be caused by one of the following conditions:

• A firewall between where the Exchange Server Analyzer is being run and the target domain controller.
  
  
• A DNS error.
  
  

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11004

Destination Protocol Unreachable

Request failed because the destination computer does not respond to the packet's protocol.

This error may be caused by a firewall between where the Exchange Server Analyzer is being run and the target domain controller.

11005

Destination Port Unreachable

Request failed because the port on the destination computer is unavailable.

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11006

No Resources

Request failed because of insufficient network resources.

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11007

Bad Option

Request failed because it contains an invalid option.

This error is unlikely because the Exchange Server Analyzer generates a standard request.

11008

Hardware Error

Request failed because of a hardware error.

Validate that the domain controller is suitably operational by running the hardware health check tool supplied by the manufacturer of your computer.

11009

Packet Too Big

Request failed because the packet that contains the request is larger than the maximum transmission unit (MTU) of a router or gateway node that is located between the source and the destination. The MTU defines the maximum size of a transmittable packet.

The request sent by the Exchange Server Analyzer is not bigger than 10 KB. Confirm that the routers and gateways in your organization are appropriately configured.

For more information, see Microsoft Knowledge Base article 159211, "Diagnoses and Treatment of Black Hole Routers" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=159211).

11010

Request Timed Out

Reply was not received in the allocated time. The default time allowed for replies is five seconds.

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11011

Bad Request

Request failed because it was encoded incorrectly.

This error is unlikely because the Exchange Server Analyzer generates a standard request.

11012

Bad Route

Request failed because there is no valid route between the source and destination computers.

For more information, see Microsoft Knowledge Base article 325487,"How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11013

TimeToLive Expired Transit

Request failed because the Time to Live (TTL) value reached zero. This causes the forwarding router or gateway node to discard the packet.

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11014

TimeToLive Expired Reassembly

Request failed because the packet was divided into fragments for transmission and all fragments were not received in the time allocated for reassembly. RFC 2460 (http://www.ietf.org/rfc/rfc2460.txt) specifies 60 seconds as the time limit within which all packet fragments must be received.

For more information, see Microsoft Knowledge Base article 325487,"How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

11015

Parameter Problem

Request failed because a router or gateway node experienced problems when it processed the packet header. This can occur if the header contains invalid field data or an unrecognized option.

This error is unlikely because the Exchange Server Analyzer generates a standard request.

11016

Source Quench

Request failed because the packet was discarded. This occurs when the output queue of the source computer has insufficient storage space. Alternatively, it can occur when packets arrive at the destination too quickly to be processed.

This error is unlikely because the Exchange Server Analyzer generates a standard request.

11017

Option Too Big

Request failed because it contains an invalid option.

This error is unlikely because the Exchange Server Analyzer generates a standard request.

11018

Bad Destination

Request failed for one of the following reasons:

• The destination IP address cannot receive PING requests.
  
  
• The destination IP address should never appear in the destination address field of any IP datagram.
  
  

This may be caused by a firewall between where the Exchange Server Analyzer is being run and the target domain controller.

11032

Negotiating IPSEC

Request failed because an IPsec connection could not be negotiated.

11050

General Failure

Request failed for an unknown reason.

For more information, see Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).