| Previous | Next |
| STATUS_INVALID_BUFFER_SIZE | STATUS_INVALID_ADDRESS_WILDCARD |
STATUS_INVALID_ADDRESS_COMPONENT
Validate the transport-address structure before looking for a routing failure
STATUS_INVALID_ADDRESS_COMPONENT is associated with the Windows transport address model rather than a generic DNS or route lookup. TDI represented a network address as one or more TA_ADDRESS elements. Each element carries an AddressLength, an AddressType, and type-specific address bytes. A provider can therefore reject an address before any packet is sent if the component does not match the selected transport format.
The useful evidence is the exact serialized address presented to the provider. Check the element count, every declared length, the address type, and the type-specific layout. For IP, the documented TA_IP_ADDRESS wrapper expects a single TDI IP address with the corresponding type and length. Do not diagnose a firewall or unreachable peer until the transport has accepted the local address representation.
TDI is deprecated, so old drivers and compatibility components are the most likely places to encounter these structures. When maintaining such code, preserve the provider name and request type in logs. A byte dump without the declared type and length is insufficient because the same bytes can be interpreted differently by different transport address families.
What to inspect
- The complete
TRANSPORT_ADDRESS/TA_ADDRESSbuffer, including element count, lengths, address types, and raw bytes. - The transport provider and operation receiving the address: address open, associate, connect, listen, query, or another TDI request.
- Any manual structure packing, size calculation, or conversion from a modern socket address into a legacy TDI address.
References
- Microsoft: TA_ADDRESS structure
- Microsoft: TA_IP_ADDRESS structure
- Microsoft: TdiDispatchCreate and TDI endpoint objects
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.