similar to: Samba4.2.2 Bind9.9.4 Centos7 Issues

On 3/21/2018 7:32 AM, David Minard via samba wrote: > Thanks Carlos, > > The thing is, that I did not upgrade the version of Samba - that is the next step, so the ports used would not have changed. I only updated the OS. > > >> On 21/03/2018, at 10:04 PM, Carlos Alberto Panozzo Cunha <carlos.hollow at gmail.com> wrote: >> >> Hi, >> I have same problem

Hai, Very important things are missing here in this one.. smb.conf Samba from sources or os provided? In case of last, centos 7.1 to 7.4 is samba 4.1.12 to 4.6.2 https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 Various packages have been rebased. Some of those are openLDAP, samba, .... And yes, as Carlos suggested, do check your firewalling also. Maybe samba didnt change but

Thanks Carlos, The thing is, that I did not upgrade the version of Samba - that is the next step, so the ports used would not have changed. I only updated the OS. > On 21/03/2018, at 10:04 PM, Carlos Alberto Panozzo Cunha <carlos.hollow at gmail.com> wrote: > > Hi, > I have same problem after update for samba. > I allow new ports in firewall. > >

G'day All, I have 4 DCs on Centos 7.1. Everything was working really well for years, including replication. Then I decided that the OS needed updating. Did the yum update on one of the DCs, rebooted. That server is now running Centos 7.4. Samba seemed to start okay. However, samba-tool drs showrepl gives this error on all 3 of the other DCs, and shows success on the updated DC.

On 27/10/15 03:57, David Minard wrote: > G'day All, > > I'm running up Samba4.2.3 with 4 DCs on Centos7. There are no > changes to the default smb.conf file that gets created at provision/DC > join. "samba-tool drs showrepl" show all DC replicating in and out. > "samba-tool dbcheck" shows no errors. > > See below for named.conf.

On 23/06/15 13:32, David Minard wrote: > I've Set up a DC and a Member Server for a file server. Both are running on Centos7 and samba version 4.2.2. The Member Server is running smbd and winbindd. > > I've followed the wiki and for the most part it's working. However, after stuffing up the ranges, then fixing them up, when I create new accounts, adding all the

> > On 24/06/15 02:55, David Minard wrote: >> On 23/06/15 13:32, David Minard wrote: >> >>> I've Set up a DC and a Member Server for a file server. Both are >>> running on Centos7 and samba version 4.2.2. The Member Server is >>> running smbd and winbindd. >>> >>> I've followed the wiki and for the most part

On 01/07/15 03:30, samba-request at lists.samba.org wrote: > Message: 17 > Date: Mon, 29 Jun 2015 08:30:52 +0100 > From: Rowland Penny<rowlandpenny at googlemail.com> > To:samba at lists.samba.org > Subject: Re: [Samba] Winbindd Strangeness > Message-ID:<5590F42C.8050002 at gmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On

G'day Guys, I've hit a snag. After using S4 from Alpha, beta, rc, 4.0.1..16 with success, I wanted to upgrade to the 4.1 series. However, after compiling, installing, and provisioning, with no errors, samba4 won't start correctly. I did a few tests by installing from scratch, on the same server each of the following versions (4.0.17, 4.0.18, 4.0.19, and 4.1.9), and got the same

Hi David, > Just to clarify, is it only the DC that doesn't return desired values of HomeDirectory and Shell? Yes, it is only the DC that doesn't pull HomeDirectory and Shell via rfc2307. (when using winbindd) Member servers with winbindd do pull the desired values without problems, I have it setup like this and it works without problems. I have only two ideas to solve your problem:

On 25/06/15 13:44, David Minard wrote: >> On 24/06/15 02:55, David Minard wrote: >>> On 23/06/15 13:32, David Minard wrote: >>> >>>> I've Set up a DC and a Member Server for a file server. Both are >>>> running on Centos7 and samba version 4.2.2. The Member Server is >>>> running smbd and winbindd.

I've Set up a DC and a Member Server for a file server. Both are running on Centos7 and samba version 4.2.2. The Member Server is running smbd and winbindd. I've followed the wiki and for the most part it's working. However, after stuffing up the ranges, then fixing them up, when I create new accounts, adding all the Unix attributes, the UID_Number is not showing the correct value

G'day All, I'm running up Samba4.2.3 with 4 DCs on Centos7. There are no changes to the default smb.conf file that gets created at provision/DC join. "samba-tool drs showrepl" show all DC replicating in and out. "samba-tool dbcheck" shows no errors. See below for named.conf. I'm having two issues. 1) After bind first starts up

G'day Rowland, > On 29/09/15 15:30, David Minard wrote: >> I'm working on a brand new set of Samba DCs, as our University changed it's domain name, so we thought we'd start from scratch. Working on 4.2.3 at the moment. >> >> I finally got the new DC to join, but I had to wait until things got quiet (midnight-ish). >> >> > Getting confused now,

Thank you Felix. On 02/07/15 16:18, Felix Matouschek wrote: > Hi David, > > I experienced this issue as well, it's currently a limitation of Samba 4.2.2. > Samba 4.2.2 DCs do not support pulling home directories and login shells from AD via rfc2307. > > I solved this issue with the "template homedir" and "template shell" directives. > You lose some

G'day All, We are trying to raise the level of our test samba4 DCs. Our windows dude wants the Domain level to be 2012_R2. I am referencing: https://wiki.samba.org/index.php/Raising_the_Functional_Levels#Supported_Functional_Levels We managed to get both domain and forest levels to 2008 R2 - forest was 2003. However, when we try to raise further, we are getting what seems to be a

Hi, I know there've been some workarounds on this topic, however I'm missing the reason for winbind to behave differently on a DC and on a member server (I also had to work around that problem and I'd really like it fixed). If there's a technical reason for it, it'd be nice to know about it. If there isn't, then it's just a bug that should be fixed. Could someone of

G'day All, I'm new to AD and the following things are causing issues trying to integrate our existing unix based infrastructure into AD. I may well be doing something wrong or just missing something, but I'm going to ask anyway. I'm stuck. We've been running Apple's OD (LDAP, Kerberos, and some Apple magic) with samba3 for years. With W7+ we need AD to

G'day All, I am not sure if this is the right place to ask, but here goes. Back ground: The Uni I work at runs their corporate MS AD. I work in the School of Computing, and we've set up our own AD (Samba4), and have it tailored to suite our needs. We manage our own accounts separately from the corporate accounts. However, our dean wants "single-sign on". From his

G'day All, We are trying to set up SCCM-5.0. Our AD test is Samba-4.8.5. SCCM requires schema changes, and Samba is rejecting these. Anyone tackled this? Ideas on how to proceed? The output thrown by the SCCM exe (extadsch.exe) is: Microsoft System Center Configuration Manager v5.00 (Build 8634) Copyright (C) 2011 Microsoft Corp. Failed to extend the Active Directory schema. Your