Yes, installing winbind is now required in more scenarios than before
when using 4.3.x.
Thanks for reporting back. I am going to mark this bug as being fixed.
If anyone is still experiencing issues, please file a new bug. Thanks.
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix
Original reporter here: the issue is resolved, with the qualification
that at my site (AD configuration) this required the installation of
winbind. Installing winbind was necessary and sufficient to resolve the
issue both in 4.3.8 and 4.3.9.
--
You received this bug notification because you are
No the original reporter either, but I can confirm that my Win7+ and
Ubuntu clients can access shares on my Samba file servers after this
update was applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not the original bug reporter, but I can confirm that I can now access
shares on Windows 7 servers. It prompted for a password (even though the
Windows machines are setup to not ask for credentials), but entering my
password for my own system worked. Shared printers are working again
too.
Thanks!
Today's Samba update may contain the fix for this issue:
http://www.ubuntu.com/usn/usn-2950-2/
Could the original bug reporter please test the update and comment here?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update: can confirm installing winbind works, but has to be all DCs and
must restart samba-ad-dc afterwards.
NB currently remote testing only so no Windows tests; however per server
testing with
smbclient -L ip.add.re.ss -U
works where before add winbind and restarting samba-ad-dc it fails
--
Have tried both workarounds listed above, doesn't appear to resolve the
issue. Setting client use spnego = no does change the error message
though, from:
NT_STATUS_OBJECT_NAME_NOT_FOUND
to
NT_STATUS_INVALID_PARAMETER
--
You received this bug notification because you are a member of Ubuntu
** Changed in: samba (Ubuntu)
Importance: Undecided => High
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding windbind is not a fix. I use samba at the most basic level, and
the last thing I want to do is add more dependencies to it to patch
broken basic functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@mmaurice Have you checked that winbindd is actually running?
IIRC between 4.1 and 4.2 the parameter for winbindd in the 'server
services =' line in /etc/samba/smb.conf changed from 'winbind' to
'winbindd'. This will have been picked up automatically if the line only
had "+" and "-" entries, or
Winbind already installed and I still have the problem.
We solved it by adding this in global section, in /etc/samba/smb.conf :
client use spnego = no
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming that installing winbind resolves the issue. Thank you @bernd-
eg.
I would propose that winbind be upgraded to a Recommends rather than a
Suggests for the Samba package.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I had similar problems. Installing winbind and libnss-winbind seems to
have fixed it. Before that, i tried upgrading to Ubuntu 16.04 and
switching dns backend from bind9_flatfile to samba internal, maybe that
helped as well.
--
You received this bug notification because you are a member of
I just downgraded back to 4.1.6, hoping to get our domain controllers
operational again, but the samba-ad-dc service fails to start with:
Unknown process model 'standard'.
In the smbd log file (attached) I note entries "msg: schema: metadata
tdb not initialized at
Attaching smbclient debug output at log level 10
** Attachment added: "smbclient debug log"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573221/+attachment/4642469/+files/smbclient.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attaching the smbd log file at debuglevel 10.
** Attachment added: "smbd log file"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1573221/+attachment/4642461/+files/smbd.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573221
Title:
I noticed that after the update to 4.3.8 my smbd would not run at all.
testparm gave me this:
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: Ignoring invalid value 'share' for parameter 'security'
Error loading
** Description changed:
Since the upgrade from 4.1.6 to 4.3.8 on our Samba domain controllers on
Ubuntu 14.04, clients fail to connect. Tested with Windows 7, Windows
Server 12 and Samba clients.
$ smbclient -L dc01 -U Administrator
session setup failed:
19 matches
Mail list logo
