| Previous | Next |
| RPC_NT_PROXY_ACCESS_DENIED | RPC_NT_NO_MORE_ENTRIES |
RPC_NT_COOKIE_AUTH_FAILED
RPC over HTTP cookie authentication failed
RPC_NT_COOKIE_AUTH_FAILED belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_COOKIE_AUTH_FAILED, mS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.
This status is also tied to RPC over HTTP. It indicates that the proxy rejected the connection because the cookie authentication step did not validate.
The useful evidence is HTTP-layer proxy logging, cookie issuance and replay, TLS termination, time skew, and whether another device strips or rewrites authentication headers or cookies before the request reaches the RPC proxy.
What to check for RPC_NT_COOKIE_AUTH_FAILED
- Capture HTTP status, proxy logs, and cookie lifetime around the failed RPC connection.
- Verify that TLS termination and load balancing preserve the cookie expected by the RPC proxy.
- Compare failures by browser/proxy profile only if the RPC client shares the same proxy authentication infrastructure.
References for RPC_NT_COOKIE_AUTH_FAILED
- Microsoft RPC: using HTTP as an RPC transport
- Microsoft Open Specifications: MS-RPCH roles and dialects
- Microsoft Open Specifications: MS-RPCH protocol details
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.