similar to: Updating from <= 4.1.11 Question

Thanks for the explanation. I have a few more sites which I will test today and feedback if a manual sync of the DNS partition solves the problem as well. Alexander On 3. March 2020 at 18:54:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: So, the reason this happens is if in the long time replication to this DC has been broken the local idea of the DNS layout for the other

Exactly! On 3. March 2020 at 11:07:02, L.P.H. van Belle via samba (samba at lists.samba.org) wrote: Just to confirm this. Im guessing you use this part : > For the DsREplicatSync error, i would suggest these steps first. > DC2, change the resolv.conf, set DC1 first, then DC2, reboot. > Wait 5 min, now check replication again, if its ok, now you can change > the

OK, found this post from Louis and this fixed it for me. https://lists.samba.org/archive/samba/2019-April/222278.html @Andrew: thanks so much for your time, effort and support the last days! Alexander On 3. March 2020 at 10:01:59, Alexander Harm (alexander.harm at apfel-q.de) wrote: That did the trick for manual replication via samba-tool drs replicate dc02 dc01 dc=ds,dc=example,dc=com

That did the trick for manual replication via samba-tool drs replicate dc02 dc01 dc=ds,dc=example,dc=com --sync-all --local -d 9 However, if I run samba-tool drs showrepl it shows me a result 1326 (WERR_LOGON_FAILURE) and also samba-tool drs replicate dc02 dc01 dc=ds,dc=example,dc=com --full-sync fails with the same error. How can I fix this? On 3. March 2020 at 04:23:02, Andrew

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

Hi there, I would like to continue on this one. I applied the patch but am wondering which package it influences. If it is just the two mentioned than it did not fix the error. Regards, Alexander On 8. February 2020 at 09:46:11, Alexander Harm (alexander.harm at apfel-q.de) wrote: Hi Andrew, I applied your patch to the Debian packages of Louis. Do you happen to know in which package it

Hi there, I was wondering, if there are any more ideas regarding this matter. Have a nice weekend, Alexander On 12. February 2020 at 07:07:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: I've been busy with other matters, including a serious issue with SCOPE_ONELEVEL searches ( https://gitlab.com/samba-team/samba/-/merge_requests/1125). If this is urgent or

Hi Andrew, no offence. I was just wondering if I could get around this issue if I nuke my Samba DCs and start fresh? Regards, Alexander On 12. February 2020 at 07:07:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: I've been busy with other matters, including a serious issue with SCOPE_ONELEVEL searches ( https://gitlab.com/samba-team/samba/-/merge_requests/1125).

On 1/12/2017 3:47 PM, Richard via samba wrote: > Hi > > root at dc1:~ # samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes > ...some error information... > Checked 3647 objects (2 errors) > root at dc1:~ # samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix > Checking 3647 objects > Checked 3647 objects (0 errors) > > root at dc1:~ # getfacl

Hi James, thanks a lot. However, in the Windows Sites & Services application the connection in question does not show up at all. It is only visible in the samba-tool output and only for the objects DomainDnsZones and ForestDnsZones... Best regards Johannes Am 27.06.2017 um 17:16 schrieb Johannes Engel: > > Hi James, > > thanks a lot. However, in the Windows Sites &

I remain baffled as to why richard.h cannot access the sysvol share. Permissions all seem ok from what I can see and I'm not sure why this should be any different from normal AD share behaviour (our other shares are working fine for domain users) I would really appreciate it if someone could let me know whether the sysvol has become corrupt in some way and I am wasting my time even trying

Hi Andrew, you can use my name if you want (Alexander Harm). I will try and build with your patch. Alexander On 8. February 2020 at 00:30:02, Andrew Bartlett (abartlet at samba.org) wrote: Thanks. At this stage is looks like a bug in the repl_meta_data module. Try the attached patch. Can I name you in the bug and is there any affiliation (eg employer) you would like named?

On Mon, 2017-03-06 at 15:48 -0500, lingpanda101 via samba wrote: > On 3/6/2017 12:53 PM, Mircea Husz wrote: > > > > -------------------------------------------- > > On Mon, 3/6/17, lingpanda101 via samba <samba at lists.samba.org> > > wrote: > > > >   Subject: Re: [Samba] DC site replication issue ? > >   To: samba at lists.samba.org > >  

I think the 6month period comes from the "tombstoneLifetime" attribute present under this DN. The default is 180 days. dn: CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration, BASEDN Can this value be reduced and wait for samba to purge the old deleted objects? Modifying this value has other implications as per AD docs but I wonder if it can be changed for a simple directory

Thanks for your invaluable help. I proceeded as advised and installed the patched packages. Still an error though, debug.txt attached. Regards, Alexander On 10. February 2020 at 11:17:02, L.P.H. van Belle via samba (samba at lists.samba.org) wrote: Hai Alexander, I had a quick look, sorry for all the absence but im very buzzy atm with some office work. A quick howto for add this in the

Hi, as instructed I upgraded to ?Version 4.11.6-Debian?. Attached the new debug file. Regards, Alexander On 7. February 2020 at 10:01:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: I would fix that first, please run Samba 4.11. We have done much on replication since then and I'm keen to rule out things we have already fixed before digging into this further.

Hi All, Trying to avoid making this into a "Me too" response :) but this is the single largest issue I have with Samba at the moment, I've struggled with this for literally years, both before I switched to rfc2307 (which did help in many areas) and since switching. I am following this thread with great interest, in the hope that I can get my GPOs working, too. Currently I've

Hi Andrew, thanks for your feedback. What are my options now? Nuke the whole thing? Alexander On 24. February 2020 at 02:08:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: G'Day Alexander, This is looking trickier than I had hoped. I don't think the patch I included is the right approach, and I can't reproduce what I thought was the issue on master.

Any update on this one? Is there anything I can do from my side? I?m prepared to nuke my Samba DC?s and start afresh if necessary. Currently I have three sites not picking up changes so I?m getting a bit anxious here? On 10. February 2020 at 19:52:02, Andrew Bartlett (abartlet at samba.org) wrote: Thanks. This is a different issue. I'll continue the thread on-list once I get to work.

On 1/2/2018 4:05 PM, Rowland Penny wrote: > On Tue, 2 Jan 2018 15:52:57 -0500 > lingpanda101 <lingpanda101 at gmail.com> wrote: > >> On 1/2/2018 3:37 PM, Rowland Penny wrote: >>> On Tue, 2 Jan 2018 15:23:18 -0500 >>> lingpanda101 <lingpanda101 at gmail.com> wrote: >>> >>> >>>> Actually it looks as if Bind isn't running.