| Previous | Next |
| RPC_S_UNSUPPORTED_AUTHN_LEVEL | RPC_S_NOT_RPC_ERROR |
RPC_S_NO_PRINC_NAME
Authenticated binding cannot obtain a server identity
RPC_S_NO_PRINC_NAME means the RPC server has not registered or cannot supply the principal name required by the selected authentication service. A principal name binds authentication to the intended server identity; it is not interchangeable with an arbitrary hostname returned by the peer.
Verify server startup calls RpcServerRegisterAuthInfo with the expected authentication service and principal, and that service-account/SPN registration matches deployment. On the client, do not query an untrusted server for a name and accept it blindly for mutual authentication. Compare the configured principal with the identity under which the service actually runs.
What to inspect
- Log the principal and authentication service registered by the server.
- Validate SPN ownership and duplicate registrations in the directory.
- Use an independently trusted expected principal for mutual authentication.
References
- Microsoft: registering RPC server authentication
- Microsoft: principal names and mutual authentication
- Microsoft: RPC principal-name concepts
Looking for a different code? Search another status or error code.