Samba refuses to authenticate "The specified network password is not correct."

  • My NAS has been basically unusable for a while now, I used to have functioning samba shares on it, but lately they will not work at all, spitting out the title error "The specified network password is not correct." I made another thread on this but it was originally for a different error and that one died anyway.


    Here is what logs tell me if I try to login with the only standard user account I have on the NAS:


    [2022/05/02 01:57:31.722427, 3] ../../source3/auth/auth.c:203(auth_check_ntlm_password)

    check_ntlm_password: mapped user is: [MicrosoftAccount]\[Exhaust]@[EXHAUSTPC]

    [2022/05/02 01:57:31.723129, 3] ../../source3/passdb/lookup_sid.c:1710(get_primary_group_sid)

    Forcing Primary Group to 'Domain Users' for Exhaust

    [2022/05/02 01:57:31.724063, 3] ../../libcli/auth/ntlm_check.c:446(ntlm_password_check)

    ntlm_password_check: NTLMv2 password check failed

    [2022/05/02 01:57:31.724178, 3] ../../libcli/auth/ntlm_check.c:492(ntlm_password_check)

    ntlm_password_check: Lanman passwords NOT PERMITTED for user Exhaust

    [2022/05/02 01:57:31.724293, 3] ../../libcli/auth/ntlm_check.c:639(ntlm_password_check)

    ntlm_password_check: LM password and LMv2 failed for user Exhaust, and NT MD4 password in LM field not permitted

    [2022/05/02 01:57:31.724918, 2] ../../source3/auth/auth.c:344(auth_check_ntlm_password)

    check_ntlm_password: Authentication for user [Exhaust] -> [Exhaust] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1


    Here is what I get if I login with root:


    [2022/05/05 20:58:13.077553, 3] ../../auth/ntlmssp/ntlmssp_server.c:509(ntlmssp_server_preauth)

    Got user=[root] domain=[MicrosoftAccount] workstation=[EXHAUSTPC] len1=24 len2=262

    [2022/05/05 20:58:13.077788, 3] ../../source3/auth/auth.c:200(auth_check_ntlm_password)

    check_ntlm_password: Checking password for unmapped user [MicrosoftAccount]\[root]@[EXHAUSTPC] with the new password interface

    [2022/05/05 20:58:13.077864, 3] ../../source3/auth/auth.c:203(auth_check_ntlm_password)

    check_ntlm_password: mapped user is: [MicrosoftAccount]\[root]@[EXHAUSTPC]

    [2022/05/05 20:58:13.078020, 3] ../../source3/auth/check_samsec.c:398(check_sam_security)

    check_sam_security: Couldn't find user 'root' in passdb.

    [2022/05/05 20:58:13.078084, 2] ../../source3/auth/auth.c:344(auth_check_ntlm_password)

    check_ntlm_password: Authentication for user [root] -> [root] FAILED with error NT_STATUS_NO_SUCH_USER, authoritative=1

    [2022/05/05 20:58:13.078212, 2] ../../auth/auth_log.c:635(log_authentication_event_human_readable)


    The server is an Odroid HC4 running OMV on top of Debian, I'm trying to connect from a Windows 10 PC. The user account I'm trying to login with was made using the Debian CLI, not with OMV, but I did go out of my way to grant permissions to this account on the samba share in OMV. It's exactly the same share that worked fine last week, without any changes besides deleting and re-making an OMV user.


    Any idea on what to do about this? I straight up cannot currently move any files to or from my NAS right now, I need to fix this.

  • Exhaust Creating a user account via the webUI ( the intended method) also creates a matching entry in the samba password database in the background. If you create an linux account on OMV via the CLI you'd have to create a matching samba password manually. You cannot access your SMB shares on OMV from anywhere if the account password is missing from the samba password database as you cannot authenticate the connection. This is separate to any issue re: authorisation which is governed by the share & file permissions.


    Root doesn't have, and never should have, a matching samba db entry.


    Just create the appropriate user account via the webUI to ensure a working configuration.

  • Exhaust Creating a user account via the webUI ( the intended method) also creates a matching entry in the samba password database in the background. If you create an linux account on OMV via the CLI you'd have to create a matching samba password manually. You cannot access your SMB shares on OMV from anywhere if the account password is missing from the samba password database as you cannot authenticate the connection. This is separate to any issue re: authorisation which is governed by the share & file permissions.


    Root doesn't have, and never should have, a matching samba db entry.


    Just create the appropriate user account via the webUI to ensure a working configuration.

    You are a LIFE SAVER my friend! That was exactly the problem. I didn't make a new account on the OMV ui just to see if I could get it working from command line, so I just added my username and password to samba on cli and it worked perfect. Thank you!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!