| Previous | Next |
| ERROR_NDIS_OFFLOAD_POLICY | ERROR_NDIS_OFFLOAD_PATH_REJECTED |
ERROR_NDIS_OFFLOAD_CONNECTION_REJECTED
TCP Chimney target rejected a connection identifies a scoped API or runtime boundary rather than a general machine failure. The offload target declined the particular TCP connection after the host considered it for offload.
Read the status in context
TCP offload is an optimization below a valid host TCP connection in an investigation of TCP Chimney target rejected a connection. An offload refusal can coexist with correct host-stack transport, so eligibility and data transfer need separate checks for the TCP Chimney target rejected a connection case.
The local policy may permit offload and the IP path may be valid; this result is the target-specific decision for one connection. Keep the numeric value, declared return type, and first returning operation together with ERROR_NDIS_OFFLOAD_CONNECTION_REJECTED; the same integer can belong to a different status namespace in another API.
Diagnostic facts
| Capture | Diagnostic value |
|---|---|
| Connection state, TCP options, target capabilities, adapter/driver version, and offload block list. | Identifies the concrete object and operation associated with TCP Chimney target rejected a connection. |
| Target completion status and whether neighboring connections on the same path offload. | Separates argument or lifecycle state from the provider beneath TCP Chimney target rejected a connection. |
| ETW/network trace showing the first offload eligibility decision in an investigation of TCP Chimney target rejected a connection. | Creates a stable before-and-after comparison for TCP Chimney target rejected a connection. |
| Known-good connection and adapter state captured on the same Windows build for the TCP Chimney target rejected a connection case. | Shows whether TCP Chimney target rejected a connection is the first result or a translated summary. |
For TCP Chimney target rejected a connection, preserve known-good connection and adapter state captured on the same Windows build while evaluating TCP Chimney target rejected a connection before reinstalling, rebooting, clearing state, or substituting another device or provider. A success observed only after such a change is useful comparison data for TCP Chimney target rejected a connection, but it does not identify the original cause.
Verification path
- Test a simple connection without unusual TCP options to the same peer. Repeat the original supported operation so the check remains relevant to TCP Chimney target rejected a connection.
- Query target capabilities and compare the rejected connection attributes. Keep unrelated inputs fixed so the change remains attributable to TCP Chimney target rejected a connection.
- Verify data transfer correctness with offload disabled as a control in an investigation of TCP Chimney target rejected a connection. Record the first returned status and any state transition observed during TCP Chimney target rejected a connection.
What the result does not prove
| Observed comparison | Next conclusion to test |
|---|---|
| The first control changes the result | Concentrate on the variable isolated by this check: Test a simple connection without unusual TCP options to the same peer. |
| The second comparison for TCP Chimney target rejected a connection reproduces the same first status | Preserve lower-layer provider, driver, service, or runtime evidence before editing application data. The second controlled check was: Query target capabilities and compare the rejected connection attributes. |
| A different status replaces TCP Chimney target rejected a connection after the bounded change | The operation moved to another boundary after the third controlled check. That check was: Verify data transfer correctness with offload disabled as a control for the TCP Chimney target rejected a connection case. Retain both results and interpret the replacement through its own API contract for TCP Chimney target rejected a connection. |
Closing the incident
Targeted correction. Update or configure the target driver, remove unsupported connection features where safe, or keep the connection on the host stack. For TCP Chimney target rejected a connection, modify only the object, argument, policy, provider, or lifecycle state identified by the collected evidence.
Acceptance criterion. Supported connections offload reliably and rejected ones fall back without reset, data loss, or retry storms. Re-run the original operation that produced TCP Chimney target rejected a connection under its original identity and supported configuration, then keep one negative control that still produces the expected neighboring outcome.
Technical references
These owner-maintained or standards-based sources define the namespace and subsystem contract needed to verify ERROR_NDIS_OFFLOAD_CONNECTION_REJECTED on the deployed platform version.
- Microsoft Open Specifications: HRESULT values — defines the status namespace used for TCP Chimney target rejected a connection.
- Microsoft: HRESULT facility extraction — documents the API or lifecycle boundary behind TCP Chimney target rejected a connection.
- Microsoft: full TCP offload — provides ABI, implementation, or protocol context for TCP Chimney target rejected a connection.
- Microsoft: NDIS Chimney interfaces — supports the portability and verification limits for TCP Chimney target rejected a connection.
Looking for a different code? Search another status or error code.