| Previous | Next |
| PEER_E_CONNECTION_FAILED | PEER_E_CONNECTION_REFUSED |
PEER_E_CONNECTION_NOT_AUTHENTICATED
Where the peer stack rejects the operation
PEER_E_CONNECTION_NOT_AUTHENTICATED — HRESULT 0x8063010A marks the transport connection was reached, but graph or group authentication did not produce an accepted secure peer relationship. Treat it as a graph lifecycle result rather than a generic peer-networking failure.
Peer Graphing maintains a connected set of nodes, replicates records and exposes separate graph, node, connection and event lifetimes. A graph database being open is not the same as the node being connected.
Evidence to preserve before retrying
- Record the first failing surface among PeerGroupConnectByAddress, graph SSP callbacks and group security validation.
- Preserve local and remote identities, certificate/GMC chains, SSP package, security callback result, clock state, address-based connection parameters and the first cryptographic error.
- Place successful creation or discovery, state-changing events and the failing call on one timeline.
- Keep peer names, identities, record identifiers, invitation data and endpoints in their original Unicode or binary representation.
Controlled isolation
Repeat against a peer with a freshly verified identity or group credential while keeping endpoint and graph/group IDs unchanged. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.
| Checkpoint | Question for this HRESULT |
|---|---|
| Before the API | Was the required node or connection state obtained in this process and user context? |
| At the HRESULT | Preserve local and remote identities, certificate/GMC chains, SSP package, security callback result, clock state, address-based connection parameters and the first cryptographic error. |
| After correction | repair identity, credential-chain or SSP validation and preserve the rejected chain for analysis; opening firewall ports cannot correct failed authentication. |
Neighboring result
PEER_E_CONNECTION_FAILED differs because generic connection failure can occur before authentication; it proves the attempt advanced to the security boundary. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Repair identity, credential-chain or SSP validation and preserve the rejected chain for analysis; opening firewall ports cannot correct failed authentication. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
- Microsoft: About the Peer Graphing API — it uses this source for the documented peer boundary.
- Microsoft Open Specifications: Peer-to-Peer Graphing Protocol
- Microsoft: Security Service Providers for Peer Graphing
- Microsoft: Common Peer Infrastructure return codes
Looking for a different code? Search another status or error code.