| Previous | Next |
| RPC_NT_BINDING_INCOMPLETE | RPC_NT_UNSUPPORTED_AUTHN_LEVEL |
RPC_NT_COMM_FAILURE
Communication failure during an RPC call
RPC_NT_COMM_FAILURE belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_COMM_FAILURE, 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 the transport-visible failure path after binding has advanced far enough for communication to be attempted. It can be caused by connection reset, broken named pipe, firewall state, server process exit, protocol framing failure, or a proxy cutting the stream.
Do not stop at the generic RPC status. Identify the protocol sequence and the last observed packet or pipe operation. A TCP capture, named-pipe trace, and server event log can lead to different answers.
What to check for RPC_NT_COMM_FAILURE
- Record the protocol sequence, endpoint, and network address used by the binding.
- Check whether the failure occurs before request transmission, while waiting for response, or during large fragment transfer.
- Correlate with server restart, service crash, firewall reset, proxy timeout, or authentication renegotiation.
References for RPC_NT_COMM_FAILURE
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC introduction
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.