Export (0) Print
Expand All
Expand Minimize

Active Directory round-trip response error

[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: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Win32_PingStatus Microsoft Windows® Management Instrumentation (WMI) class to determine the value (StatusCode key) that is returned from the Active Directory® directory service server. Win32_PingStatus returns an object with 24 properties that supply extensive details about the ping packets that the class sends.

If the Exchange Server Analyzer finds that the value for this key matches one of the values in the following table, an error is displayed.

The Exchange Server Analyzer displays the Active Directory server name and the corresponding StatusCode value that is returned with this error.

 

StatusCode value Meaning Description

11001

Buffer Too Small

This error is unlikely to be returned because the Exchange Server Analyzer is generating 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 information, see the 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 information, see Active Directory server down or unreachable.

Alternatively, this error may be caused by a firewall between where the Exchange Server Analyzer is being run and the target domain controller, or even a DNS error.

For information, see the 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 not available.

For information, see the 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 information, see the 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 to be returned because the Exchange Server Analyzer is generating a standard request.

11008

Hardware Error

Request failed because of a hardware error.

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

11009

Packet Too Big

Request failed because the packet that contains the request is larger than the maximum transmission unit (MTU) of a node (router or gateway) located between the source and 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 in size. Confirm that the routers and gateways in your organization are appropriately configured.

For information, see the 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 within the allocated time. The default time allowed for replies is five seconds.

For information, see the 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 is unlikely to be returned because the Exchange Server Analyzer is generating a standard request.

11012

Bad Route

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

For information, see the 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 its Time to Live (TTL) value reached zero, which causes the forwarding node (router or gateway) to discard the packet.

For information, see the 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 within 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 information, see the 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 node (router or gateway) encountered problems while processing the packet header. This status occurs if, for example, the header contains invalid field data or an unrecognized option.

This is unlikely to be returned because the Exchange Server Analyzer is generating a standard request.

11016

Source Quench

Request failed because the packet was discarded. This occurs when the source computer's output queue has insufficient storage space, or when packets arrive at the destination too quickly to be processed.

This is unlikely to be returned because the Exchange Server Analyzer is generating a standard request.

11017

Option Too Big

Request failed because it contains an invalid option.

This is unlikely to be returned because the Exchange Server Analyzer is generating a standard request.

11018

Bad Destination

Request failed because the destination IP address cannot receive PING requests or 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 be not negotiated.

11050

General Failure

Request failed for an unknown reason.

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

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft