| Previous | Next |
| ERROR_CONNECTED_OTHER_PASSWORD | ERROR_BAD_USERNAME |
ERROR_CONNECTED_OTHER_PASSWORD_DEFAULT
The connection succeeded with default credentials.
ERROR_CONNECTED_OTHER_PASSWORD_DEFAULT is Win32 result 2109 (0x83D). The requested network connection exists after the call, but Windows authenticated it with credentials already available to the logon session or provider rather than the explicit password path the caller expected. Like 2108, it is not an ordinary connection failure.
Why default credentials take over
- the caller omits a password or user name and permits the provider to use the current logon identity
- an existing authenticated session to the server satisfies the new resource connection
- credential-manager or provider state supplies a default identity for the target
- interactive logic falls back to current credentials after the requested credential path is unavailable
- a deployment wrapper interprets the qualified-success code as an error and retries unnecessarily
Identity evidence without secrets
Record the API and flags, remote UNC name, local device, network provider, requested user-name form, current logon/session identity, pre-existing server connections, result 2109, and the effective connected user returned by supported queries. Do not log passwords, tickets, credential blobs, or hashes that can be replayed.
Diagnostic sequence
Confirm the connection exists and identify the effective account. Enumerate existing connections to the same server because Windows may reuse session authentication. Compare the result with the application’s authorization expectation, not just with connectivity.
If a specific account was required, inspect whether the API arguments and flags actually forced that identity and whether an existing server session prevented a new credential context. Test in a fresh logon session before blaming the remote server.
Safe handling
Accept the connection only when the effective identity is authorized for the requested action. Otherwise close application work, remove or isolate conflicting connections through a deliberate workflow, and reconnect under the intended account.
Automation should expose “connected as default identity” as a distinct outcome. Never assume successful access proves that the explicit secret was validated, and do not store an unused password as though it were current.
Difference from ERROR_CONNECTED_OTHER_PASSWORD
Result 2108 says a different password was obtained during the connection attempt. Result 2109 says the connection was made with default credentials already selected by Windows or the network provider.
Example
A management utility requests a share while the operator already has an authenticated SMB session to that server. The WNet call returns 2109 and access works under the operator’s account. The utility verifies that identity before performing an administrative upload.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: Windows Networking (WNet)
- Microsoft: WNetUseConnection
- Microsoft: WNetGetUser
Looking for a different code? Search another status or error code.