| Previous | Next |
| STATUS_LINK_TIMEOUT | STATUS_INVALID_ADDRESS |
STATUS_INVALID_CONNECTION
The transport connection handle is not valid
These statuses describe transport endpoint and connection state. For STATUS_INVALID_CONNECTION, they can appear below higher-level file sharing, DFS, redirector, RPC, or networking code before the error is translated to Win32 or Winsock form.
The caller supplied a connection object or handle that the transport cannot use. This is usually a lifetime or handle-management problem rather than a network outage.
For STATUS_INVALID_CONNECTION, for diagnostics, capture the endpoint address, address family, connection object, local and remote close/reset events, timeout, route, ICMP condition when available, and the higher-level component that issued the transport request.
What to inspect
- Trace connection object creation and teardown.
- Check for use-after-close or stale cached connection handles.
- Confirm the handle belongs to the expected transport endpoint.
References for STATUS_INVALID_CONNECTION
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Sockets error codes
- Microsoft Open Specifications: DFS client product behavior
Looking for a different code? Search another status or error code.