But you can only reproduce it with windows 10 as the client, right? Not
with smbclient and protocol SMB3?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1736940
Title:
Ubuntu 16.04
> Uhm, so I should ENABLE the service, and then prevent it from
starting?
You would be adding a condition for it to start. Native systemd services
can have such conditions in the service definition file, but in xenial
samba is not one of those I'm afraid. In fact, the samba package has a
mess of
Sorry, I can't debug those scripts. I don't know why all your users show
up as nobody/nogroup in smbstatus, maybe you have a force user setting
in smb.conf or something like that?
Regarding the unknown protocol issue, that's a valid bug, but probably
at a level of "low".
--
You received this
I think we should be ok with the new test case.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1572745
Title:
Samba server amd64 testcast fails step 28. net usersidlist could not
That being said, the linked samba bug is interesting:
https://bugzilla.samba.org/show_bug.cgi?id=13124
samba git master still has that change, i.e., use addr (ip) instead of
ldap_server_name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
> ldapsearch -x -Z -h I.P -p 389 -D
cn=administrator,cn=users,dc=techmint,dc=lan -w -b
'dc=techmint,dc=lan'
Please use -ZZ. And did you use the IP for -h? Why not the hostname,
which I think (from a previous comment you made) is win.cifs.com?
> I am able to confirm with tcpdump that
The packages built, so obviously the FTBFS fix is applied. Marking as
verified.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iproute2 in Ubuntu.
I can see something similar from an ubuntu artful client if I force protocol
SMB3:
andreas@nsnx:~$ smbclient //10.0.100.215/ubuntu -U ubuntu%ubuntu -m SMB3
WARNING: The "syslog" option is deprecated
Domain=[XENIAL-SAMBA-SMBSTATUS-1737534] OS=[] Server=[]
smb: \>
server (xenial):
PID
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-2113
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1576799
Title:
Regression: 2:4.3.8+dfsg-0ubuntu0.14.04.2
I can confirm this behavior in xenial, but to be honest I'm not sure
what's the correct expected outcome.
Can you perhaps accomplish something similar using /usr/sbin/policy-
rc.d? You can create that script and it would check if samba is the
service being started, and then check if the disk you
Taking a look.
** Changed in: samba4 (Ubuntu)
Status: Incomplete => New
** Changed in: samba4 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
In particular, one of the fixes introduced in samba 4.3.7 was to
properly check certificates, as @mdeslaur said in comment #2:
"o CVE-2016-2113 (Missing TLS certificate validation)"
So I would ask you to double check your certificates and chain to make
sure all is correct in that front, as
You probably removed python2 from your system, or something like that.
Check the first line of /usr/bin/pyclean to be sure.
This is beyond a bug report now. Something you did broke your system
with regards to python.
My last suggestion is to try to reinstall the python2.7-minimal package,
either
13 matches
Mail list logo
