| Previous | Next |
| ERROR_DUP_NAME | ERROR_NETWORK_BUSY |
ERROR_BAD_NETPATH
A Windows UNC path is resolved in layers. MUP first determines which registered UNC provider can claim a prefix such as \server\share; the selected redirector then handles the remote file-system operation. WNet resource APIs similarly separate the network resource portion from the path that is later handled by ordinary file APIs.
That makes the exact failing prefix important. A valid server with a misspelled share, a DFS or provider prefix that is not claimed, and a transport failure after a share has been established are different conditions even when a UI presents all of them as a network path problem.
Diagnose the path by boundary
- Reduce the target from the full file path to \server\share and test the resource boundary first.
- Use the same spelling of the server and share when comparing clients; aliases can select different authentication or provider paths.
- If WNetGetResourceInformation is used, retain its provider/type result and any ERROR_EXTENDED_ERROR details.
- Do not begin with file ACL changes until the share prefix itself is known to resolve.
Windows MUP and UNC prefix resolution · WNetGetResourceInformation · MS-SMB2 TREE_CONNECT
Looking for a different code? Search another status or error code.