| Previous | Next |
| STATUS_VHDSET_BACKING_STORAGE_NOT_FOUND | STATUS_SMB_BAD_CLUSTER_DIALECT |
STATUS_SMB_NO_PREAUTH_INTEGRITY_HASH_OVERLAP
STATUS_SMB_NO_PREAUTH_INTEGRITY_HASH_OVERLAP occurs during SMB 3.1.1 negotiation when the peers have no common preauthentication-integrity hash function. This is a negotiated security capability mismatch, not a bad password or a missing share.
How to narrow it down
Preauthentication integrity protects the SMB3.1.1 Negotiate and Session Setup exchange against tampering and downgrade attempts; its hash contributes to session key derivation. Record the dialect, negotiate contexts, offered hash algorithms and any device that inspects or transforms SMB traffic. A legacy appliance, proxy or partial implementation can be relevant even when both endpoints claim SMB support.
Do not disable the security property just to complete the connection. Update the incompatible implementation or remove the component that prevents compatible negotiation.
Evidence that matters
- Capture SMB2 NEGOTIATE contexts and the algorithms offered by each side.
- Check intermediary devices that may alter or terminate SMB traffic.
- Upgrade the incompatible implementation rather than bypassing preauthentication protection.
References
- Microsoft Open Specifications: NTSTATUS reference
- Microsoft: SMB security enhancements
- MS-SMB2: SMB2 SESSION_SETUP processing
Looking for a different code? Search another status or error code.