samba - Mar 2026 - Auth failiure

Hi
We have an industrial robot with an older Linux version that (suddenly)
cant connect to the network share where the control files are stored. The
server is set to NT1 auth due to the fact that the robot does not support
SMB2 or higher.

The robot has a GUI where we enter SERVER, SHARE, FOLDER, DOMAIN, USER and
PASSWORD. No error message when the connection fails.

If we use the *same connection and credential details* on another Linux or
Windows workstation, then the connection works as expected.

1. From the robot/workstation log on member server

[2026/03/11 11:15:39.127782,  3]
source3/auth/auth.c:202(auth_check_ntlm_password)
  auth_check_ntlm_password: check_ntlm_password:  Checking password for
unmapped user [HPX]\[bock]@[ROBOMAC-213-TF-514826] with the new password
interface
[2026/03/11 11:15:39.127788,  3] source3/auth/auth.c:208
(auth_check_ntlm_password)
  auth_check_ntlm_password: check_ntlm_password:  mapped user is:
[HPX]\[bock]@[ROBOMAC-213-TF-514826]

2. Log on DC

[2026/03/11 11:15:39.137306,  2]
auth/auth_log.c:860(log_authentication_event_human_readable)
  Auth: [SamLogon,network] user [HPX]\[bock] at [Wed, 11 Mar 2026
11:15:39.137289 CET] with [NTLMv1] status [NT_STATUS_WRONG_PASSWORD]
workstation [\\\\ROBOMAC-213-TF-514826] remote host [ipv4:10.0.2.11:50678]
mapped to [HPX]\[bock]. local host [ipv4:10.0.2.15:49152]  NETLOGON
computer [HP-SRV03$] trust account [HP-SRV03$]

3. On member server

[2026/03/11 11:15:39.160820,  5]
source3/auth/auth.c:265(auth_check_ntlm_password)
  auth_check_ntlm_password: winbind authentication for user [bock] FAILED
with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2026/03/11 11:15:39.160838,  2]
source3/auth/auth.c:353(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [bock] -> [bock] FAILED
with error NT_STATUS_WRONG_PASSWORD, authoritative=1

Where do I go from here? I was thinking of installing tcpdump on the member
server to get a complete network trace dump.

I should also mention that this has worked in the past. Don't know when it
ceased to work though.

-- 
------ -------------------- 8 ------------------ ------
IT truism: "A permanent solution is a temporary solution that works so well
that noone want to replace it."

Anders ?stling
+46 768 716 165 (Mobil)

On Fri, 13 Mar 2026 10:04:44 +0100
Anders ?stling via samba <samba at lists.samba.org> wrote:
> Hi
> We have an industrial robot with an older Linux version that
> (suddenly) cant connect to the network share where the control files
> are stored. The server is set to NT1 auth due to the fact that the
> robot does not support SMB2 or higher.
> 
> The robot has a GUI where we enter SERVER, SHARE, FOLDER, DOMAIN,
> USER and PASSWORD. No error message when the connection fails.
> 
> If we use the *same connection and credential details* on another
> Linux or Windows workstation, then the connection works as expected.
> 
> 1. From the robot/workstation log on member server
> 
> [2026/03/11 11:15:39.127782,  3]
> source3/auth/auth.c:202(auth_check_ntlm_password)
>   auth_check_ntlm_password: check_ntlm_password:  Checking password
> for unmapped user [HPX]\[bock]@[ROBOMAC-213-TF-514826] with the new
> password interface
> [2026/03/11 11:15:39.127788,  3] source3/auth/auth.c:208
> (auth_check_ntlm_password)
>   auth_check_ntlm_password: check_ntlm_password:  mapped user is:
> [HPX]\[bock]@[ROBOMAC-213-TF-514826]
> 
> 2. Log on DC
> 
> [2026/03/11 11:15:39.137306,  2]
> auth/auth_log.c:860(log_authentication_event_human_readable)
>   Auth: [SamLogon,network] user [HPX]\[bock] at [Wed, 11 Mar 2026
> 11:15:39.137289 CET] with [NTLMv1] status [NT_STATUS_WRONG_PASSWORD]
> workstation [\\\\ROBOMAC-213-TF-514826] remote host
> [ipv4:10.0.2.11:50678] mapped to [HPX]\[bock]. local host
> [ipv4:10.0.2.15:49152]  NETLOGON computer [HP-SRV03$] trust account
> [HP-SRV03$]
> 
> 3. On member server
> 
> [2026/03/11 11:15:39.160820,  5]
> source3/auth/auth.c:265(auth_check_ntlm_password)
>   auth_check_ntlm_password: winbind authentication for user [bock]
> FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
> [2026/03/11 11:15:39.160838,  2]
> source3/auth/auth.c:353(auth_check_ntlm_password)
>   check_ntlm_password:  Authentication for user [bock] -> [bock]
> FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
> 
> Where do I go from here? I was thinking of installing tcpdump on the
> member server to get a complete network trace dump.
> 
> I should also mention that this has worked in the past. Don't know
> when it ceased to work though.
> 
These things don't suddenly stop working for no reason, they usually
stop working after an update or a change, so what got updated or
changed ?
Failing that, there is little to go on, more details will be required.

Rowland