| Previous | Next |
| ERROR_REM_NOT_LIST | ERROR_BAD_NETPATH |
ERROR_DUP_NAME
The key word is name, not IP address. Legacy Windows networking and NetBIOS distinguish name registration from transport addressing. RFC 1001 and RFC 1002 define unique and group NetBIOS names and the registration/conflict procedures used to determine whether a name can be owned by a node.
A duplicate-name result therefore should be investigated as an identity collision. Changing share permissions or SMB file ACLs cannot resolve it. In mixed or legacy networks, capture the computer/NetBIOS name being registered and the node that already answers for it; in a domain-join workflow also verify that the intended computer identity is the one being provisioned.
What separates this from path errors
- ERROR_DUP_NAME concerns ownership of a network name; ERROR_BAD_NET_NAME concerns locating a named resource.
- Check duplicate host/computer naming before changing credentials.
- On NetBIOS-over-TCP networks, examine name registration and name-service traffic rather than only SMB TREE_CONNECT traffic.
- After renaming a node, verify that stale registrations and cached name resolution no longer identify the old owner.
RFC 1001 NetBIOS concepts and methods · RFC 1002 NetBIOS detailed specification · Windows MUP and UNC prefix resolution
Looking for a different code? Search another status or error code.