** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD DC aft
Do you want to mark this as resolved/closed/fixed/whatever the correct
status on launchpad is?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords
Good news!
I installed the update and rebooted and it did not work, smbclient
commands returned NT_STATUS_NO_LOGON_SERVERS. But after also adding
"client ipc signing = auto" to smbd.conf as per Tony Haley's
recommendation in comment #20, and after another reboot, it is working
as expected with jus
Hi all,
I will try to remember to test the samba update after the users leave
for the day, as I have to take the new PDC which works offline in order
to test this. The "libsoup" thing referred to in the link that Marc
provided does not seem relevant to us, as we did not even have that
package inst
>I had to add client ipc signing = auto to the global section of the
smb.conf file too.
This fixed it for me too (not sure if this was only a configuration
issue or the regression combined with config issue).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ug 1572824] Re: Samba Domain Member cannot check passwords against
Samba AD DC after "Badlock" update
For what it's worth, I saw the same symptoms as the original reporter
and there has not been any change after upgrading to
2:3.6.25-0ubuntu0.12.04.3
--
You received this bug not
For what it's worth, I saw the same symptoms as the original reporter
and there has not been any change after upgrading to
2:3.6.25-0ubuntu0.12.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157282
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.
https://b
** 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.
https://bugs.launchpad.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD DC after
"Badlock" update
To manage notif
This should be fixed ASAP as it is causing large scale issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD DC after
"Ba
The RPC errors make me think this may be related to the DCERPC problems
that were causing problems with domain trust functions in bug #1572122 .
A source code patch is available in Samba but has not been applied or
tested in Ubuntu.
--
You received this bug notification because you are a member o
Does anyone have anything better than do a fresh install from a new
version of Ubuntu?
There's got to be a better option...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain
Since it only took me 3-5 hours to build a 16.04 LTS AD DC running 4.3.8
and the bind DNS backend, I suspect that this might just be the easiest
way to go.
Just to repeat as a warning, upgrading my existing DC from 4.1.6 to
4.3.8 on 14.04 LTS resulted in a broken DC for me, so rather than just
upg
Hi all,
I appear to have solved this issue for myself by setting up an entirely
new AD DC today based on 16.04 LTS, and joining it to the existing
domain. I took no action at all on the affected system, and yet today
after setting that new system up, the affected system seems to be
connecting prop
Here is a wireshark capture of the connection attempt.
** Attachment added: "Wireshark Capture"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572824/+attachment/4643368/+files/SMB.pcapng.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
A portion of the log file from when a Windows Workstation tries to
connect to the server.
** Attachment added: "log.smdb"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572824/+attachment/4643353/+files/log.smdb.tar.gz
--
You received this bug notification because you are a member of
Here are my package versions:
libsmbclient:amd64 2:4.3.8+dfsg-0ubuntu0.14.04.2amd64
libwbclient0:amd64 2:4.3.8+dfsg-0ubuntu0.14.04.2amd64
python-samba2:4.3.8+dfsg-0ubuntu0.14.04.2amd64
python-smbc 1.0.14.1-0ubuntu2 amd64
samba2:4.3.8+dfsg-0ubuntu0.14.04.2amd64
samba-common2:4.3.8+dfsg-0ub
Adding a "Me Too".:
I have the exact issue.
I have tried various things to no avail. Here is my Global section of
my SMB.CONF:
[global]
workgroup = BNB
realm = BNB.LAN
netbios name = DC1
server role = active directory domain controller
#dns forwarder = 12
I also ran into a problem looking like this one. My smb.conf global
section looks like this:
[global]
netbios name = SERVER
realm = EXAMPLE.COM
workgroup = EXAMPLE
security = ADS
kerberos method = system keytab
mangled names = no
log level = 2
I have a feeling Kerberos authenticatio
Whoops, that's supposed to be example.org, to match with the above. I
was changing my organization name.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check
To be clear, neither example.org or example.com are my actual samba
domain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD D
I am not running winbind on the DC. The options I have tried in their
various combinations are server signing = off, server signing = auto,
and client signing = off. I have tried them on just the 12.04 server,
and also on both the 12.04 server and the AD DC. Nothing seems to
resolve the problem for
Here is my current samba AD DC config, after removing the signing
option:
# Global parameters
[global]
workgroup = SAMDOM
realm = samdom.example.com
netbios name = FILESERV2
server role = active directory domain controller
server services = -dns
os
You've tried setting server signing = disabled on your 12.04 LTS server?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD DC a
Are you running winbind on your AD DC?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD DC after
"Badlock" update
To manage
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/1572824
Title:
Samb
27 matches
Mail list logo