| Previous | Next |
| RPC_S_PROTOCOL_ERROR | RPC_S_UNSUPPORTED_TRANS_SYN |
RPC_S_PROXY_ACCESS_DENIED
This status belongs to the RPC over HTTP transport path
RPC_S_PROXY_ACCESS_DENIED is relevant when RPC is tunneled with the ncacn_http protocol sequence and an HTTP proxy participates in the route. It is not the same as the RPC server rejecting interface access or the endpoint mapper denying an RPC call.
RPC/HTTP can carry separate credentials and authentication settings for the RPC proxy and, in newer credential structures, an HTTP proxy server. A transport connection may therefore fail at the proxy before RPC authentication with the target server is established.
What to check
- Confirm that the binding actually uses
ncacn_httpand identify every proxy between the client and RPC proxy. - Inspect proxy authentication policy and the credentials supplied in the RPC HTTP transport credentials structure.
- Compare a denied request with proxy logs; HTTP-layer denial should be fixed at the proxy, not by changing endpoint UUIDs or RPC procedure numbers.
- Separate HTTP proxy authentication from the RPC authentication service configured on the binding.
Testing the target server with direct TCP RPC may prove server availability, but it does not validate the RPC-over-HTTP proxy route that produced this status.
References
Looking for a different code? Search another status or error code.