smbpasswd stops working post-upgrade

Issues related to configuring your network
MartinR
Posts: 274
Joined: 2015/05/11 07:53:27
Location: UK

smbpasswd stops working post-upgrade

Postby MartinR » 2016/06/01 11:28:01

Background

I have a network of machines behind an air-gap, therefore upgrades are a tedious business normally performed four times per year. Last weekend I applied the updates to the 5.11 machines that were current on 18 April 2016. Those of my users who run Windows boxes (Windows 7 Enterprise) map Samba shares on my machines to a drive letter on their PCs. In order to do this they need to keep their Samba passwords updated. Samba passwords are held in /etc/samba/passdb.tdb.

Problem

Users are reporting that password setting fails. This seems to be a fairly solid issue:

Code: Select all

$ smbpasswd
Old SMB password:
New SMB password:
Retype new SMB password:
machine 127.0.0.1 rejected the negotiate protocol. Error was : NT_STATUS_ACCESS_DENIED.
Password changed for user XXXX

$ smbclient -L YYYY
Enter XXXX's password:
cli_negprot: SMB signing is mandatory and the server doesn't support it.
protocol negotiation failed: NT_STATUS_ACCESS_DENIED

$ smbclient -V
Version 3.6.23-12.el5_11
$ uname -a
Linux YYYY 2.6.18-409.el5 #1 SMP Tue Mar 15 18:13:50 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux

$ smbpasswd -D3
added interface ib0 ip=:::::%ib0 bcast=::ffff:ffff:ffff:ffff%ib0 netmask=ffff:ffff:ffff:ffff::
added interface eth2 ip=:::::%eth2 bcast=::ffff:ffff:ffff:ffff%eth2 netmask=ffff:ffff:ffff:ffff::
added interface eth1 ip=:::::fe%eth1 bcast=::ffff:ffff:ffff:ffff%eth1 netmask=ffff:ffff:ffff:ffff::
added interface ib0 ip=... bcast=...255 netmask=255.255.255.0
added interface eth1 ip=... bcast=...255 netmask=255.255.255.0
added interface eth2 ip=... bcast=...255 netmask=255.255.255.0
Old SMB password:
New SMB password:
Retype new SMB password:
Connecting to 127.0.0.1 at port 445
cli_negprot: SMB signing is mandatory and the server doesn't support it.
machine 127.0.0.1 rejected the negotiate protocol. Error was : NT_STATUS_ACCESS_DENIED.
Password changed for user XXXX


The first attempt at setting a password is what the users see. Next I tried using smbclient to determine if it was a problem just for smbpasswd, it appears not to be so. I enclose the relevant version strings, smbpasswd doesn't appear to report its version to the command line. I then ran with debugging and this confirmed that the issues was the same.

All work was done on the local machine. XXXX is my username YYYY is the machine's simple name. IP addresses have been stripped of meaningful information but were consistent. No other network problems are apparent.

Issues

[*]What has changed? smb.conf is the same, yet I've never seen cli_negprot: SMB signing is mandatory and the server doesn't support it before.
[*]The message Password changed for user XXX is wrong; the password has not been changed.

MartinR
Posts: 274
Joined: 2015/05/11 07:53:27
Location: UK

Re: smbpasswd stops working post-upgrade

Postby MartinR » 2016/06/07 14:00:44

Bump

stevemowbray
Posts: 295
Joined: 2012/06/26 14:20:47

Re: smbpasswd stops working post-upgrade

Postby stevemowbray » 2016/06/07 14:28:03

Perhaps related to this bug?
https://bugzilla.redhat.com/show_bug.cgi?id=1326918

In which case the only current fix is to downgrade your samba packages.

MartinR
Posts: 274
Joined: 2015/05/11 07:53:27
Location: UK

Re: smbpasswd stops working post-upgrade

Postby MartinR » 2016/06/07 15:41:38

Thanks. I've printed off the bug report. yum downgrade doesn't help so my options seem to be to try to install Samba from CentOS 5.10 (yuk - if possible) or else move to using the 3x images and see if they work.

MietekN
Posts: 1
Joined: 2016/08/25 08:20:39

Re: smbpasswd stops working post-upgrade

Postby MietekN » 2016/08/25 08:24:02

Set in the [global] section of smb.conf
client ipc signing = auto