Cfrgtkky

I have had Samba working for years with Server version 16. This morning, I upgraded to 18.04 LTS, and Windows XP now gets

System error 1326 has occurred.

Logon failure: unknown user name or bad password.

I have always had Samba configured to us pam to sync with system passwords. I also ran smbpasswd manually, but it did not help.

Active lines of smb.conf:

[global]







  workgroup = RHFACTOR



   dns proxy = no



   log file = /var/log/samba/log.%m



   max log size = 1000



   syslog = 0



   panic action = /usr/share/samba/panic-action %d



   server role = standalone server



   passdb backend = tdbsam



   obey pam restrictions = yes



   unix password sync = yes



   passwd program = /usr/bin/passwd %u



   passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:*%nn *passwordsupdatedssuccessfully* .



   pam password change = yes



   map to guest = bad user



   usershare max shares = 10



   usershare allow guests = no



[share0]



  comment = share0 zero



  path = /winbackup/zero



  browsable = yes



  guest ok = no



  read only = no



  create mask = 0755

(Three more shares identical to above, except for share name and directory.

I reviewed the Samba and AppArmor sections of the 18.04 manual. I tried disabling AppArmor and restarting Samba, but it made no difference.

Samba is doing its best to keep up with the Win10s and macOSs of the world so it has moved on.

Add these lines in the [global] section of smb.conf:

lanman auth = yes

ntlm auth = yes

Then restart smbd:

sudo service smbd restart

Note: I remember coming across a situation where you actually had to degrade the max server smb dialect used in addition to the lines above:

server max protocol = NT1

That would be a travesty. I don't know how a Win10 machine would ever be able to connect to it.