| Previous | Next |
| STATUS_NOT_SUPPORTED | STATUS_DUPLICATE_NAME |
STATUS_REMOTE_NOT_LISTENING
STATUS_REMOTE_NOT_LISTENING localizes a failure before a usable remote session exists: the target endpoint was contacted or identified, but the service expected by the redirector was not listening. It is therefore different from a missing share name or a share permission denial. In an SMB incident, the useful question is whether the server side exposed the required SMB service for the transport and dialect that the client actually attempted.
How to narrow it down
Record the server name, resolved address, transport, connection time and the first protocol request that was attempted. A successful name lookup does not prove that a file-service listener is available. Conversely, changing share ACLs cannot repair a listener that never accepted the session.
When validating a non-Windows implementation, test the same server and share with a protocol-aware client and explicit name-resolution settings. Samba documents that server and service names are separate parts of an SMB resource name and that its client can be directed to a specific address for diagnosis.
Evidence that matters
- Confirm which service endpoint the client reached and whether the server accepted the connection at that moment.
- Separate hostname resolution from listener availability by recording the resolved address and the connection result.
- Inspect server-side SMB/service logs before changing share permissions or credentials.
References
Looking for a different code? Search another status or error code.