Troubleshooting • Re: Samba authentication error on one but not another Raspi

I'm confused.

Are you connecting from a Pi to a share on a Windows 11 box or from a Windows11 box to a share on each Pi?

Assuming it's the latter...

• Both your smb.conf have map to guest = bad user which means invalid/unknown usernames get mapped to guest access. When that happens any password is ignored.
  This and the error you're seeing implies that the username you're using from the client exists as a Samba user but the password is not what you expect it to be.
  Be aware that with unix password sync = yes if you change the Samba user's password the matching Linux user's password will also be changed to match.
• Some further points that need attention but are not likely to be the cause of the problem:
  • available = yes is the default so does not need to be specified.
  • You have both read only = no and writable = yes in your share definitions. They mean the same thing so only one of them is needed.
  • You have valid users = jason and public = yes in your share definitions. public = yes enables guest access but valid users = jason restrict access to only the Samba user jason. IIRC if you connect to the server as a guest user called jason you still won't be able to access the share.

I have tried adding the below but it didn't work.

Code:

#client min protocol = SMB3#client max protocol = SMB3#client smb encrypt = required#client signing = required#server min protocol = SMB3#server max protocol = SMB3#ntlm auth = ntlmv2-only

If you put those into your smb.conf exactly as written they would have changed nothing as they're commented out.

Lastly, this is what I'd be inclined to try:

1. Shutdown Samba on the broken box
2. Backup your smb.conf
3. Change unix password sync = yes to unix password sync = no
4. Start Samba
5. Change the Samba user jason's password to what you believe it should be.
6. Retry the login from the client.

Statistics: Posted by thagrol — Sat Dec 27, 2025 11:56 pm

---