| Previous | Next |
| STATUS_FILE_RENAMED | STATUS_NO_SECURITY_ON_OBJECT |
STATUS_VIRTUAL_CIRCUIT_CLOSED
STATUS_VIRTUAL_CIRCUIT_CLOSED couples two facts: the request exceeded its timeout interval and the remote session was disconnected. It is therefore stronger than a slow-operation warning; the current conversation with the server is no longer valid for subsequent requests.
How to narrow it down
Capture the request type, timeout value, last successful activity and whether the server was under load. A long read, a blocked write, an encrypted transfer and a stuck server operation can look similar at the client, but they need different evidence. Samba documents per-request timeout control for its client, illustrating why the configured timeout must be logged with the incident.
Reconnect at the protocol boundary. Do not continue to submit operations through the old session, and verify the outcome of any mutating request that was outstanding when it closed.
Evidence that matters
- Record configured timeouts and the last confirmed response from the server.
- Separate a request timeout from a deliberate remote disconnect.
- Re-establish a session and validate incomplete writes before retrying them.
References
- Microsoft Open Specifications: NTSTATUS reference
- Samba: smbclient manual
- Microsoft: Get-SmbConnection
Looking for a different code? Search another status or error code.