| Previous | Next |
| RPC_NT_INVALID_NET_ADDR | RPC_NT_INVALID_TIMEOUT |
RPC_NT_NO_ENDPOINT_FOUND
RPC_NT_NO_ENDPOINT_FOUND is an NTSTATUS value used by the Windows RPC runtime. An RPC binding can be only partially bound: it may name a protocol sequence and host without naming a concrete endpoint. This status means endpoint resolution did not produce a usable endpoint for the requested binding. The binding text can therefore be valid even though the requested server interface cannot be reached through an endpoint.
This is not the same as RPC_NT_INVALID_ENDPOINT_FORMAT, which rejects the endpoint text itself, or RPC_NT_SERVER_UNAVAILABLE, which is about server reachability after endpoint selection. It also does not automatically mean that the host name is wrong.
A valid binding did not resolve to an endpoint that can serve the call
- Determine whether the client supplied a well-known endpoint or relies on endpoint mapping/name-service resolution.
- Record the interface UUID, protocol sequence and target host used for resolution; all three affect the endpoint lookup.
- Verify server registration and endpoint advertisement before changing client retry or timeout behavior.
References
- Microsoft: Binding handles
- Microsoft: Client-side binding and endpoint discovery
- The Open Group: DCE 1.1 RPC specification
Looking for a different code? Search another status or error code.