similar to: group share problems with winbindd and samba 3.6.23-30.el6_7

I am the IT administrator for a group of researchers at a university. I have two SAMBA servers. One running CentOS 6 and one running CentOS 7. Both are running Samba 4.2.10 (4.2.10-6.el6_7 and 4.2.10-6.el7_2 respectively). When they were running the previous version of Samba everything worked fine and and both domain bound machines and non-domain bound machines could log in and mount/map both

On 13/04/16 17:55, Bill Baird wrote: > Hi All, > > I am running Samba 3.6 in PDC mode (i know, i know...AD upgrade is in the > works). > > The most recent update for CentOS 6 (samba-3.6.23-30.el6_7.x86_64) appears > to have caused issues and I was forced to downgrade back > to samba-3.6.23-25.el6_7.x86_64. > > When 3.6.23-30 is installed, users running Windows 7 x64

Hi All, I am running Samba 3.6 in PDC mode (i know, i know...AD upgrade is in the works). The most recent update for CentOS 6 (samba-3.6.23-30.el6_7.x86_64) appears to have caused issues and I was forced to downgrade back to samba-3.6.23-25.el6_7.x86_64. When 3.6.23-30 is installed, users running Windows 7 x64 receive the following error when trying access shares: "The trust relationship

On Thu, Apr 21, 2016 at 01:25:14PM +0100, Rowland penny wrote: > My understanding is that the Badlock patches fixed a multitude of security > problems, That's not disputed, and is why we have persevered in trying to make the patched version work instead of just reverting back to the previous version (you'll note that one response on this thread advocated doing that). >

hi It can be so help [global] >---admin users = @nt_admins if not then I need 1. root at pdc:~# testparm 2. root at pdc:~# ldapsearch -xLLL -H ldapi:/// -b ou=groups,ou=arkhangelsk,dc=rugion,dc=ru ldap suffix = ou=arkhangelsk,dc=rugion,dc=ru ldap group suffix = ou=groups 3. try log level = 10 max log size = 1000 and go through the authorization in windows pc

hi all I have two different Samba versions as PDC and BDC and depending on which one is "domain master" users which are domain admins are not recognized as such. Everything seems normal with 3.6.23-25.el6_7 as "domain master" but when I configure them so 4.2.10 is the master then I login to Win7 fine but Windows tells me that the user is not an Admin and I need to supply

On Wed, Apr 20, 2016 at 03:42:47PM -0500, Karen Magee wrote: > Also tied winbindd and that was a disaster of a > different sort. > > It wouldn't use the local unix groups first, which will cause way too > many issues. > > All along, however, the PCs that connect (when not trying to use > winbindd) have consistently > been able to connect and use

On 21/04/16 12:46, Ian Collier wrote: > I hear your frustration - we've had the same troubles. My understanding > of this (which may be wrong) is: > > - The Badlock patches broke something in the Samba server which > means it's no longer able to contact the Windows AD in order to > authenticate users. My understanding is that the Badlock patches fixed a

I've now tired both client ipc signing = auto or client signing = required server signing = auto --- that did not work...Also tied winbindd and that was a disaster of a different sort. It wouldn't use the local unix groups first, which will cause way too many issues. All along, however, the PCs that connect (when not trying to use winbindd) have consistently been able to connect and

CentOS Errata and Bugfix Advisory 2015:2642 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2642.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6fa40ca76f3ba80ad56ce80b2b2f787148f6d019ec15400e62871d4993bdf527 libsmbclient-3.6.23-21.el6_7.i686.rpm

CentOS Errata and Security Advisory 2016:0011 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0011.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 72950df9a934b10dfa2ba2eda29a9c67fccd7316b23d05374cd61dc7039ee9b9 libsmbclient-3.6.23-24.el6_7.i686.rpm

CentOS Errata and Security Advisory 2016:0448 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0448.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b5decc0e8074aa9e596c96b3323adab98335d5cd675cb9b51ccee1dd26353bed libsmbclient-3.6.23-25.el6_7.i686.rpm

CentOS Errata and Security Advisory 2016:0611 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0611.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d5f3744dc798fa513d4856aad3a992e836a3c6b29244fbfef4b0b42da1badbac libsmbclient-3.6.23-30.el6_7.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On Wed, May 25, 2016 at 2:38 PM, pisymbol . <pisymbol at gmail.com> wrote: > Hello: > > Platform: CentOS 6.7 x86-64 > > $ rpm -qa | grep samba > samba-common-3.6.23-30.el6_7.x86_64 > samba4-libs-4.2.10-6.el6_7.x86_64 > ie-samba-utils-3.6.13-7.x86_64 > samba-winbind-3.6.23-30.el6_7.x86_64 > samba-client-3.6.23-30.el6_7.x86_64 >

Hello: Platform: CentOS 6.7 x86-64 $ rpm -qa | grep samba samba-common-3.6.23-30.el6_7.x86_64 samba4-libs-4.2.10-6.el6_7.x86_64 ie-samba-utils-3.6.13-7.x86_64 samba-winbind-3.6.23-30.el6_7.x86_64 samba-client-3.6.23-30.el6_7.x86_64 samba-winbind-clients-3.6.23-30.el6_7.i686 samba-winbind-clients-3.6.23-30.el6_7.x86_64 Problems began after requiring SMB signing (I forgot the specifics but it was

This spnego stuff makes me think about "client ldap sasl wrapping = sign" to be added in some cases. There are threads related to that posted recently. Disabling spnego is, if I'm not mistaken, disabling Kerberos. Disabling Kerberos should not be what you really want with AD : ) 2016-05-26 13:23 GMT+02:00 pisymbol . <pisymbol at gmail.com>: > On Wed, May 25, 2016 at 2:38