| Previous | Next |
| STATUS_SHARING_PAUSED | STATUS_REDIRECTOR_PAUSED |
STATUS_REQUEST_NOT_ACCEPTED
STATUS_REQUEST_NOT_ACCEPTED is not a generic syntax error. In SMB2 it can occur when a share has reached its maximum number of uses, when a session is still in progress, or when an invalid duplicate session-binding situation is attempted. The stage of the request determines what is actually saturated or inconsistent.
How to narrow it down
Capture whether the status came from Session Setup, Tree Connect or a later operation. The SMB2 specification associates it with session state and with a share whose current uses have reached its configured maximum. Those paths require different remediation: session concurrency or binding logic on one side, share-use capacity on the other.
Do not interpret it as proof that a server is globally offline. A single service can reject a new request while other sessions and shares continue to work.
Evidence that matters
- Record the SMB command and session/tree identifiers that received the status.
- Check share-use limits separately from global server capacity.
- Avoid racing duplicate session setup or binding attempts from concurrent client workers.
References
- Microsoft Open Specifications: NTSTATUS reference
- MS-SMB2: SMB2 SESSION_SETUP processing
- MS-SMB2: SMB2 TREE_CONNECT processing
Looking for a different code? Search another status or error code.