Upgrade from Server 16 to 18.04 LTS breaks Samba shares from XP machines











up vote
0
down vote

favorite












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.










share|improve this question
























  • Are you sure the samba on XP is compatible with the versions 18.04 uses?
    – Rinzwind
    Aug 16 at 21:20










  • Check the manual. Less secure version of Samba may be disabled by default in the newer release. It can probably be re-enabled.
    – Ken Sharp
    Aug 17 at 1:28










  • Moribus1 nailed it with the lanman auth and ntlm auth parameters. Ken Sharp, there is no mention of more or less secure versions in the Ubutu manual's Samba chapter. The Samba manual I could find was mighty ugly, and I had no idea about security levels at the time
    – Sawdust and Noise
    Aug 17 at 23:37










  • If you are so inclined please mark my answer below as "accepted": askubuntu.com/help/someone-answers We win prizes based on the number of correct answers. At least I think we do - maybe not.
    – Morbius1
    Aug 18 at 13:04










  • @Morbius1 I got a mail from the head honcho of Stack and a ton of swag (heck I was allowed to pick it myself) when I won the 100k rep race ;-) +1 on the answer from me.
    – Rinzwind
    Aug 27 at 9:49

















up vote
0
down vote

favorite












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.










share|improve this question
























  • Are you sure the samba on XP is compatible with the versions 18.04 uses?
    – Rinzwind
    Aug 16 at 21:20










  • Check the manual. Less secure version of Samba may be disabled by default in the newer release. It can probably be re-enabled.
    – Ken Sharp
    Aug 17 at 1:28










  • Moribus1 nailed it with the lanman auth and ntlm auth parameters. Ken Sharp, there is no mention of more or less secure versions in the Ubutu manual's Samba chapter. The Samba manual I could find was mighty ugly, and I had no idea about security levels at the time
    – Sawdust and Noise
    Aug 17 at 23:37










  • If you are so inclined please mark my answer below as "accepted": askubuntu.com/help/someone-answers We win prizes based on the number of correct answers. At least I think we do - maybe not.
    – Morbius1
    Aug 18 at 13:04










  • @Morbius1 I got a mail from the head honcho of Stack and a ton of swag (heck I was allowed to pick it myself) when I won the 100k rep race ;-) +1 on the answer from me.
    – Rinzwind
    Aug 27 at 9:49















up vote
0
down vote

favorite









up vote
0
down vote

favorite











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.










share|improve this question















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.







upgrade 18.04 samba windows-xp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 17 at 1:26









Organic Marble

10.4k63257




10.4k63257










asked Aug 16 at 21:11









Sawdust and Noise

32




32












  • Are you sure the samba on XP is compatible with the versions 18.04 uses?
    – Rinzwind
    Aug 16 at 21:20










  • Check the manual. Less secure version of Samba may be disabled by default in the newer release. It can probably be re-enabled.
    – Ken Sharp
    Aug 17 at 1:28










  • Moribus1 nailed it with the lanman auth and ntlm auth parameters. Ken Sharp, there is no mention of more or less secure versions in the Ubutu manual's Samba chapter. The Samba manual I could find was mighty ugly, and I had no idea about security levels at the time
    – Sawdust and Noise
    Aug 17 at 23:37










  • If you are so inclined please mark my answer below as "accepted": askubuntu.com/help/someone-answers We win prizes based on the number of correct answers. At least I think we do - maybe not.
    – Morbius1
    Aug 18 at 13:04










  • @Morbius1 I got a mail from the head honcho of Stack and a ton of swag (heck I was allowed to pick it myself) when I won the 100k rep race ;-) +1 on the answer from me.
    – Rinzwind
    Aug 27 at 9:49




















  • Are you sure the samba on XP is compatible with the versions 18.04 uses?
    – Rinzwind
    Aug 16 at 21:20










  • Check the manual. Less secure version of Samba may be disabled by default in the newer release. It can probably be re-enabled.
    – Ken Sharp
    Aug 17 at 1:28










  • Moribus1 nailed it with the lanman auth and ntlm auth parameters. Ken Sharp, there is no mention of more or less secure versions in the Ubutu manual's Samba chapter. The Samba manual I could find was mighty ugly, and I had no idea about security levels at the time
    – Sawdust and Noise
    Aug 17 at 23:37










  • If you are so inclined please mark my answer below as "accepted": askubuntu.com/help/someone-answers We win prizes based on the number of correct answers. At least I think we do - maybe not.
    – Morbius1
    Aug 18 at 13:04










  • @Morbius1 I got a mail from the head honcho of Stack and a ton of swag (heck I was allowed to pick it myself) when I won the 100k rep race ;-) +1 on the answer from me.
    – Rinzwind
    Aug 27 at 9:49


















Are you sure the samba on XP is compatible with the versions 18.04 uses?
– Rinzwind
Aug 16 at 21:20




Are you sure the samba on XP is compatible with the versions 18.04 uses?
– Rinzwind
Aug 16 at 21:20












Check the manual. Less secure version of Samba may be disabled by default in the newer release. It can probably be re-enabled.
– Ken Sharp
Aug 17 at 1:28




Check the manual. Less secure version of Samba may be disabled by default in the newer release. It can probably be re-enabled.
– Ken Sharp
Aug 17 at 1:28












Moribus1 nailed it with the lanman auth and ntlm auth parameters. Ken Sharp, there is no mention of more or less secure versions in the Ubutu manual's Samba chapter. The Samba manual I could find was mighty ugly, and I had no idea about security levels at the time
– Sawdust and Noise
Aug 17 at 23:37




Moribus1 nailed it with the lanman auth and ntlm auth parameters. Ken Sharp, there is no mention of more or less secure versions in the Ubutu manual's Samba chapter. The Samba manual I could find was mighty ugly, and I had no idea about security levels at the time
– Sawdust and Noise
Aug 17 at 23:37












If you are so inclined please mark my answer below as "accepted": askubuntu.com/help/someone-answers We win prizes based on the number of correct answers. At least I think we do - maybe not.
– Morbius1
Aug 18 at 13:04




If you are so inclined please mark my answer below as "accepted": askubuntu.com/help/someone-answers We win prizes based on the number of correct answers. At least I think we do - maybe not.
– Morbius1
Aug 18 at 13:04












@Morbius1 I got a mail from the head honcho of Stack and a ton of swag (heck I was allowed to pick it myself) when I won the 100k rep race ;-) +1 on the answer from me.
– Rinzwind
Aug 27 at 9:49






@Morbius1 I got a mail from the head honcho of Stack and a ton of swag (heck I was allowed to pick it myself) when I won the 100k rep race ;-) +1 on the answer from me.
– Rinzwind
Aug 27 at 9:49












1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










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.






share|improve this answer





















  • Great. How did you know this was the way to go?
    – Marc Vanhoomissen
    Aug 29 at 12:08










  • DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
    – thomas-peter
    Oct 7 at 10:49











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1066035%2fupgrade-from-server-16-to-18-04-lts-breaks-samba-shares-from-xp-machines%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted










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.






share|improve this answer





















  • Great. How did you know this was the way to go?
    – Marc Vanhoomissen
    Aug 29 at 12:08










  • DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
    – thomas-peter
    Oct 7 at 10:49















up vote
2
down vote



accepted










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.






share|improve this answer





















  • Great. How did you know this was the way to go?
    – Marc Vanhoomissen
    Aug 29 at 12:08










  • DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
    – thomas-peter
    Oct 7 at 10:49













up vote
2
down vote



accepted







up vote
2
down vote



accepted






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.






share|improve this answer












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.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 16 at 21:51









Morbius1

1,216127




1,216127












  • Great. How did you know this was the way to go?
    – Marc Vanhoomissen
    Aug 29 at 12:08










  • DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
    – thomas-peter
    Oct 7 at 10:49


















  • Great. How did you know this was the way to go?
    – Marc Vanhoomissen
    Aug 29 at 12:08










  • DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
    – thomas-peter
    Oct 7 at 10:49
















Great. How did you know this was the way to go?
– Marc Vanhoomissen
Aug 29 at 12:08




Great. How did you know this was the way to go?
– Marc Vanhoomissen
Aug 29 at 12:08












DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
– thomas-peter
Oct 7 at 10:49




DIdn't work for me. The last thing I was expecting was to have to reinstall 16.04 on my file server. Ubuntu have really taken a big step backwards with the 18.04 release. I shudder when I realise that this is the LTS release. It's bad on so many other levels.
– thomas-peter
Oct 7 at 10:49


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1066035%2fupgrade-from-server-16-to-18-04-lts-breaks-samba-shares-from-xp-machines%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Quarter-circle Tiles

build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

Mont Emei