| Previous | Next |
| STATUS_REMOTE_DISCONNECT | STATUS_LINK_FAILED |
STATUS_REMOTE_RESOURCES
STATUS_REMOTE_RESOURCES identifies resource pressure at the remote endpoint. The client reached a remote computer, but that system could not allocate what the request required. It should not be treated as a local memory diagnosis or as evidence that a share name is invalid.
How to narrow it down
Measure the server state at the incident: memory pressure, open-session count, request queues, SMB credits, disk latency, file handles and any appliance-specific limits. Then compare the request pattern with the normal workload. A burst of many parallel opens may require client-side throttling even when individual requests are well formed.
Use a retry policy with backoff and a hard ceiling. Resource exhaustion can worsen if every client immediately opens replacement connections or retries large transfers at full concurrency.
Evidence that matters
- Correlate the error with server resource telemetry, not only client logs.
- Record the operation size and concurrency that preceded the failure.
- Bound retries and reduce parallel work while the server recovers.
References
Looking for a different code? Search another status or error code.