| Previous | Next |
| STATUS_DUPLICATE_NAME | STATUS_NETWORK_BUSY |
STATUS_BAD_NETWORK_PATH
STATUS_BAD_NETWORK_PATH describes a server-path problem, not a missing share. The client could not locate the network path needed to reach the named remote computer, so it has not yet reached the point where SMB can validate a share name or evaluate access rights.
How to narrow it down
Keep the server component and the share component of a UNC path separate during diagnosis. A failure for \\server\share at this stage points to name resolution, routing, transport reachability or the selected network provider; STATUS_BAD_NETWORK_NAME is the closer status when the server is reachable but the requested share cannot be connected.
Compare a named connection with a test pinned to a known address only as a diagnostic experiment. Samba documents that a server name and the IP/DNS host name can differ, and that clients may use several name-resolution mechanisms.
Evidence that matters
- Record the exact UNC server component and every address returned for it.
- Verify the route and network provider path before testing a particular share name.
- Use a protocol-aware client to distinguish server discovery from Tree Connect.
References
- Microsoft Open Specifications: NTSTATUS reference
- Samba: smbclient manual
- MS-SMB2: SMB2 TREE_CONNECT processing
Looking for a different code? Search another status or error code.