| Previous | Next |
| RPC_NT_INVALID_ASYNC_CALL | RPC_NT_COOKIE_AUTH_FAILED |
RPC_NT_PROXY_ACCESS_DENIED
RPC over HTTP proxy denied access
RPC_NT_PROXY_ACCESS_DENIED belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_PROXY_ACCESS_DENIED, 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 specific to RPC over HTTP style transport paths. The RPC client is not failing at local binding construction; the proxy layer rejected access before the RPC exchange could proceed normally.
Check proxy authentication, allowed RPC virtual directory, SSL requirements, client access policy, and whether the request is going through an expected corporate HTTP proxy or the RPC proxy itself.
What to check for RPC_NT_PROXY_ACCESS_DENIED
- Distinguish ordinary web proxy denial from RPC proxy denial in logs.
- Verify credentials, TLS/certificate trust, and configured RPC over HTTP dialect.
- Check whether the same endpoint works from a network path that bypasses the proxy.
References for RPC_NT_PROXY_ACCESS_DENIED
- 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.