| Previous | Next |
| STATUS_BAD_DEVICE_TYPE | STATUS_TOO_MANY_NAMES |
STATUS_BAD_NETWORK_NAME
STATUS_BAD_NETWORK_NAME is a share-level result. It differs from STATUS_BAD_NETWORK_PATH: the client can reach the server path, but the requested network service or share cannot be connected. In SMB2 this is a Tree Connect failure and can also carry share-redirection context for clustered storage.
How to narrow it down
Validate the server and share portions of the UNC path independently. A folder beneath a share is not itself a share name; for example, a client should connect to \\server\share and then address a subdirectory inside that tree. The server can also return this status when a requested share has moved and the request did not meet the requirements for redirect handling.
Use a share-listing or direct Tree Connect test to identify the exact name that the server offers. Samba documents the same distinction as a //server/service resource name.
Evidence that matters
- Verify the share name exactly as advertised by the server, not a directory path beneath it.
- Check whether a cluster or DFS-style redirect changed the current owner or target address.
- Compare a listing of offered services with the UNC path used by the failing client.
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.