2

I’m trying to mount a remote TrueNAS Scale Samba share from a Debian-based Ubuntu container.

The mount fails on the server with wrong password:

 ntlm_password_check: NTLMv2 password check failed [2025/01/27 19:23:14.640615, 3] ../../libcli/auth/ntlm_check.c:487(ntlm_password_check) ntlm_password_check: NEITHER

LanMan nor NT password supplied for user user1 [2025/01/27 19:23:14.641310, 2] ../../source3/auth/ auth.c:353(auth_check_ntlm_password) check_ntlm_password:
Authentication for user [user1] -> [user1] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1 [2025/01/27 19:23:14.641418, 2] ../../auth/auth_log.c:1237(log_authentication_event_human_readable) Auth: [SMB2,(null)] user [][user1] at [Mon, 27 Jan 2025 19:23:14.641387 PST] with [NTLMv2] status [NT_STATUS_WRONG_PASSWORD] workstation [docker] remote host [ipv4:192.168.10.38:57766] mapped to [][user1]. local host [ipv4:192.168.10.10:445] {"timestamp": "2025-01-27T19:23:14.641728-0800", "type": "Authentication", "Authentication": {"version": {"major": 1, "minor": 3}, "eventId": 4625, "logonId": "0", "logonType": 3, "status": "NT_STATUS_WRONG_PASSWORD", "localAddress": "ipv4:192.168.10.10:445", "remoteAddress": "ipv4:192.168.10.38:57766", "serviceDescription": "SMB2", "authDescription": null, "clientDomain": "", "clientAccount": "user1", "workstation": "docker", "becameAccount": null, "becameDomain": null, "becameSid": null, "mappedAccount": "user1", "mappedDomain": "", "netlogonComputer": null, "netlogonTrustAccount": null, "netlogonNegotiateFlags": "0x00000000", "netlogonSecureChannelType": 0, "netlogonTrustAccountSid": null, "passwordType": "NTLMv2", "clientPolicyAccessCheck": null, "serverPolicyAccessCheck": null, "duration": 3967}} [2025/01/27 19:23:14.642070, 3] ../../source3/smbd/ smb2_server.c:4050(smbd_smb2_request_error_ex)
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_LOGON_FAILURE] || at ../../source3/smbd/ smb2_sesssetup.c:147 [2025/01/27 19:23:14.771164, 3] ../../source3/ smbd/server_exit.c:229(exit_server_common) Server exit (NT_STATUS_CONNECTION_RESET)

 #My compose file: ... volumes: ... - originals:/usr/src/app/originals ... volumes: model-cache: originals: driver_opts: type: cifs o: 'iocharset=utf8,username=user1,password=passw1,rw' device: '//192.168.10.10/user1' ...

Verified the username and password used for authentication are correct. Can connect from another server with: smbclient //192.168.10.10/user1/ -U user1

Improve this question
2
  • Often, this error isn't actually caused by an incorrect password, rather, it stems from the mount not negotiating the proper SMB protocol or security mode with TrueNAS. In this situation, the server rejects the authentication attempt - displaying “NEITHER LanMan nor NT password supplied for user user1” - because the container's default settings aren't sending the password in the manner TrueNAS expects. Commented Feb 2 at 10:38
  • A common solution is to explicitly define the SMB version and security mode in the mount options. Many TrueNAS configurations require NTLMv2 authentication (typically enforced with the “ntlmssp” flag) over SMB 3.0. Adjusting the docker-compose volume options to include these settings can help resolve the issue like Syarif mentioned it. It specifies using SMB version 3.0 with the "ntlmssp" security option (via vers=3.0 and sec=ntlmssp), which ensures the mount negotiates the proper SMB protocol and security mode. Commented Feb 2 at 10:46

1 Answer 1

Reset to default
1

i see that You can connect manually when command executed on docke rhost but failed on container

to make sure, go to container terminal, and try exec manually

mount -t cifs //192.168.10.10/user1 /mnt -o username=user1,password=passw1,vers=3.0,sec=ntlmssp,iocharset=utf8

and share the output here for error if its successfully connect to share, try edit your compose file such as:

volumes: originals: driver_opts: type: cifs o: 'username=user1,password=passw1,vers=3.0,iocharset=utf8,sec=ntlmssp,rw' device: '//192.168.10.10/user1'
Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.