Windows error 67 (ERROR_BAD_NET_NAME): meaning and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: No installed network provider accepted or located the specified network resource name.

Could be also:
Constant	Type	OS
ENOLINK	errno	Linux
EPROCLIM	errno	Mac
ENOLINK	errno	Solaris
NO_SUCH_PARTITION	BugCheck Code	Windows

Previous	Next
ERROR_BAD_DEV_TYPE	ERROR_TOO_MANY_NAMES

ERROR_BAD_NET_NAME

WNetAddConnection2 documents this status when the remote resource is empty, invalid, or cannot be located by a network resource provider. WNetGetResourceInformation likewise uses it when the supplied remote name is not an existing resource for any network. This is more specific than a generic host reachability test.

For SMB paths, split the UNC into server and share. Reaching the server does not prove that the share name exists, and a provider may reject the syntax before transport is attempted. MUP provider selection and SMB TREE_CONNECT are therefore both relevant depending on the exact call path.

Test the network resource name

Preserve the exact UNC spelling, including server alias and share component.
Confirm which provider claims the path and whether the share name exists on that server.
Compare ERROR_BAD_NETPATH: path resolution can fail at a broader prefix/path boundary.
Do not replace the result with DNS lookup success; DNS and network resource naming are not equivalent.

WNetAddConnection2 · WNetGetResourceInformation · Windows MUP and UNC prefix resolution · MS-SMB2 TREE_CONNECT

Looking for a different code? Search another status or error code.