| Previous | Next |
| RPC_NT_INVALID_ENDPOINT_FORMAT | RPC_NT_NO_ENDPOINT_FOUND |
RPC_NT_INVALID_NET_ADDR
RPC_NT_INVALID_NET_ADDR is an NTSTATUS value used by the Windows RPC runtime. This status concerns the network-address component of an RPC binding. Address representation is interpreted in the context of the chosen protocol sequence, so an otherwise plausible host string can still be invalid for that transport or binding form.
It is distinct from RPC_NT_SERVER_UNAVAILABLE. Invalid network address is a binding-construction problem; server-unavailable is about attempting to reach a server after a usable binding has been established. It also differs from an invalid endpoint field.
The network address cannot be interpreted for the selected transport
- Capture the protocol sequence, network address and endpoint together from the binding source.
- Use the documented string-binding grammar and avoid applying URL or socket-address escaping rules that do not belong to RPC bindings.
- Resolve DNS, routing and firewall questions only after the binding API accepts the address representation.
References
- Microsoft: String binding
- Microsoft: RpcBindingFromStringBinding
- The Open Group: DCE 1.1 RPC specification
Looking for a different code? Search another status or error code.