| Previous | Next |
| ERROR_ALREADY_ASSIGNED | ERROR_INVALID_PARAMETER |
ERROR_INVALID_PASSWORD
WNetAddConnection2 accepts an explicit user name and password, or can use defaults from the caller context. Its documentation also notes interaction between explicit and default credentials when reconnecting to the same server. The final password error therefore needs the exact credential source, not just the typed string.
For SMB, session authentication precedes access to a share. A password failure is different from share authorization after authentication. On Samba, authenticated shares and guest services also have distinct behavior; a guest fallback or mapping policy can make a client believe it is using one identity while the server establishes another context.
Credential evidence
- Record the user name form, domain/workgroup context, and whether the password parameter was explicit, empty, or NULL.
- Check for an existing connection to the same server under another credential context.
- Inspect the server authentication log and the identity actually assigned to the session.
- Do not modify share ACLs until authentication itself succeeds.
WNetAddConnection2 · Samba smbclient manual · Samba smb.conf manual
Looking for a different code? Search another status or error code.