| Previous | Next |
| STATUS_CONNECTION_RESET | STATUS_TRANSACTION_ABORTED |
STATUS_TOO_MANY_NODES
The “nodes” are transport-managed state, not a count of reachable hosts
STATUS_TOO_MANY_NODES appears in the NTSTATUS transport-status block immediately after connection/address states, and Microsoft describes it as a transport failing to acquire another node dynamically. Public documentation does not define the node structure or bind this code to TCP, SMB, or a specific provider. The safe interpretation is provider-local transport state exhaustion, not “too many computers on the network.”
Legacy TDI documentation gives useful architecture context. A transport can expose address objects, connection endpoints, and control channels, storing object-specific state in the file object context. TDI requests are dispatched according to the type and state of that transport object. This does not prove that every STATUS_TOO_MANY_NODES producer is TDI, but it shows why internal transport bookkeeping can have capacity independently of sockets visible to a user-mode process.
Preserve the transport provider, object type, connection/address count, allocation failures, and the operation that attempted to grow state. Check whether resources are leaked after aborts or disconnects and whether the count rises monotonically across repeated tests. Increasing application retry frequency can make an internal-state leak worse. Also separate this code from STATUS_CONNECTION_COUNT_LIMIT: the latter explicitly describes a configured connection-count limit, while this status describes dynamic acquisition of transport nodes.
What to inspect
- Identify the transport provider and object type involved in the failed request.
- Graph internal object/connection counts across repeated connect-abort cycles.
- Look for state that is allocated but not released before raising configured network limits.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: TDI internal-device-control dispatch
- Microsoft: TDI_REQUEST structure
- Microsoft: TDI_CONNECT
- Microsoft: Using NTSTATUS values
Looking for a different code? Search another status or error code.