| Previous | Next |
| STATUS_CPU_SET_INVALID | STATUS_NO_USER_SESSION_KEY |
STATUS_NETWORK_OPEN_RESTRICTION
STATUS_NETWORK_OPEN_RESTRICTION is narrower than an ordinary access denial. The remote open failed because a restriction that governs network opens was not satisfied. It therefore directs diagnosis to the server policy and the open context, not simply to the spelling of the path.
How to narrow it down
Capture the open disposition, share mode, desired access, session identity, existing opens and any server policy relevant to the share. In SMB workloads, a failed create/open can depend on share settings, exclusive-open restrictions, handle state, security requirements or server-specific policy.
Do not assume that granting broader file permissions will solve it. A network-open restriction can remain in place even when the caller has the necessary file-system rights.
Evidence that matters
- Record the exact open semantics: access, sharing flags, disposition and target path.
- Compare the request with an existing successful open to the same share.
- Inspect server policy and conflicting existing handles before changing ACLs.
References
- Microsoft Open Specifications: NTSTATUS reference
- MS-SMB2: SMB2 TREE_CONNECT processing
- Samba: smbclient manual
Looking for a different code? Search another status or error code.