similar to: Performance Problems - DNS Not Responding

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.

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

Hi , Thank you for your input. I have had tried all of the escape characters you have have tested with but I have had no luck with them. I am curious to know which versions of net have you been tested with? I do agree that the best practice for this is to remove "-" from the beginning of the object name, However, seeing that it can be created that way allowed, I would like to find a

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 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,

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.

G'day All, Will replay to all messages so far in this one to keep it all together. On 21/03/18 22:52, lingpanda101 wrote: > 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 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 24/03/18 01:35, lingpanda101 wrote: > On 3/22/2018 8:06 PM, David Minard wrote: >> G'day All, >> >>     Will replay to all messages so far in this one to keep it all >> together. >> >> On 21/03/18 22:52, lingpanda101 wrote: >>> On 3/21/2018 7:32 AM, David Minard via samba wrote: >>>> Thanks Carlos, >>>>

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

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

G'day Guys, Sorry for the delay. I've had the log level of samba at 5 for a while now. Nothing interesting seems to be coming from the samba log. Increasing the bind logs, to level 5, shows nothing different. I get the same two warnings: 09-Oct-2015 12:46:01.421 database: warning: samba_dlz: Ignoring duplicate zone 'samba4.scem.westernsydney.edu.au' from

On 3/22/2018 8:06 PM, David Minard wrote: > G'day All, > >     Will replay to all messages so far in this one to keep it all > together. > > On 21/03/18 22:52, lingpanda101 wrote: >> 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 >>>

On 3/25/2018 8:54 PM, David Minard wrote: > > > On 24/03/18 01:35, lingpanda101 wrote: >> On 3/22/2018 8:06 PM, David Minard wrote: >>> G'day All, >>> >>>     Will replay to all messages so far in this one to keep it all >>> together. >>> >>> On 21/03/18 22:52, lingpanda101 wrote: >>>> On 3/21/2018 7:32 AM, David

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

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

G'day All, I've got Samba4 using Bind for its DNS, and all seems to working well, except that I've noticed occasionally that bind either dies or locks up. I see the following in the my named.log file: 02-Jul-2015 21:54:08.859 database: critical: samba_dlz: talloc: access after free error - first free may be at ../lib/ldb/common/ldb.c:1592 02-Jul-2015 21:54:08.859 database:

G'day All, I've been setting up a new set of DCs, using 4.2.3 and all was going well until I tried to get a 4th DC going. I'm using bind_DLZ, and I think this is where I went wrong. I provisioned the new DC before having set up bind properly (I forgot to "yum install bind bind-util bind-libs") before hand. The provision worked okay, except that it told me

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 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: