similar to: Failing replication

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

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

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

Hi Andrew, I applied your patch to the Debian packages of Louis. Do you happen to know in which package it will end up? Tried samba and samba-dsdb-modules but the error remains the same. Alexander On 8. February 2020 at 01:38:25, Alexander Harm (alexander.harm at apfel-q.de) wrote: Hi Andrew, you can use my name if you want (Alexander Harm). I will try and build with your patch.

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.

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

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? I've filed a bug and will file a merge request once I have a test to confirm this. https://bugzilla.samba.org/show_bug.cgi?id=14272 Thanks! Andrew Bartlett On Fri, 2020-02-07 at 23:34 +0100, Alexander

I did but these are the last lines. It ends with ?raise e? also in the shell. I also ran it on the other DCs and they all end with ?raise e?. Alexander On 7. February 2020 at 09:12:02, Andrew Bartlett (abartlet at samba.org) wrote: G'Day Alexander, It looks like you have copied the logs out of a terminal and lost the ends of the lines. Those have the critical (groan...) details of

Hai, If updated the script a bit, can you run it again? wget https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Alexander Harm via samba > Verzonden: vrijdag 16 augustus 2019 9:14 > Aan: samba at lists.samba.org > Onderwerp:

Strange, we had this working the last 6 months... only a week ago these errors started showing... So, no other idea than downgrading our Windows DC to 2016? Alexander On 6. February 2020 at 10:23:43, Rowland penny via samba (samba at lists.samba.org) wrote: On 05/02/2020 22:41, Alexander Harm via samba wrote: Hello, we could need some help resolving a replication issue we experience since one

Hello, we could need some help resolving a replication issue we experience since one week. We have 1 DC in the cloud running Windows Server 2019 with DFL/FFL 2008R2. We have 3 sites with 5 DCs running Samba on Debian Buster in total replicating the AD from Windows. Since one week the replication state shows the following error: DC=ds,DC=craze,DC=toys Azure\VMDC-AZURE-01 via RPC DSA

Hi everyone, I like to connect azure ad to my samba4 installation via AD Azure Sync (with password passthrough authentication). Passthrough authentication and User synchronizations working with a Windows 2016 domain member server without any harm. But group membership synchronizations fails always because AD Azure Sync cannot parse the member attribute (reference-value-not-ldap-conformant).

On Wed, 2 May 2018 11:14:36 -0400 Andrew Dumaresq via samba <samba at lists.samba.org> wrote: > This may be a dumb question, but will the upgrade work in 4.8.1 now? > when I follow the bug, it looks like it wasn't included... > Not a dumb question at all, but the fix for the upgrade bug never made it to 4.8.1. It definitely will be in 4.8.2 (so I am told) Rowland

Hi all, Our migration is coming along nicely, everything seems to work like it should... I thought... Only samba-tool dbcheck reports five errors: root at dc1:~# samba-tool dbcheck Checking 1143 objects ERROR: Normalisation error for attribute 'objectClass' in 'CN=phdseminar,CN=Users,DC=my,DC=samba,DC=domain' Values/Order of values do/does not match: ['top',

Hi list, Since it is considered ?harmful? to run a domain controller that acts a fileserver I was considering the option of putting the AD DC into a chroot. Is there any special configuration to perform (except bind interfaces) to avoid conflicts ? (is there any broadcasting issues or so?) Regards -- S?bastien Le Ray

So, for now, should I work my way through the DNS manager and delete any references for the old dc manually or just leave it alone? On Thu, Mar 8, 2018 at 6:16 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Thu, 2018-03-08 at 17:49 -0600, Robert Wooden via samba wrote: > > Will these DNS listings clear themselves with time or do I have a problem > > here? > >

On Mon, 2018-07-30 at 15:58 -0300, Elias Pereira wrote: > Hey @Andrew Bartlett, thanks for the link!!!It sure is already a direction !! :) > > Do you have any idea if these adjustments that Jushua said, will be part of Samba 4.9 updates? I don't think so, as the bug should have been closed in that case. You can of course re-test (sometimes bugs stay open incorrectly), but I

On Thu, 2018-03-15 at 14:34 -0400, Justin Foreman wrote: > The problem does not happen if I recreate the domain from scratch. I’m able to successfully join 4.8.0 to a 4.6.7 domain built from scratch (just tried it). One thing that I will note is that I also saw SPN creation failures when attempting to join Windows 2008 R2. So it’s not a Samba 4.8.0 problem. It’s a problem with my database

Andrew - i am trying to join a new DC. Both DCs (old and new) are running samba 4.5.12-Debian On Dec 11, 2017 8:11 PM, "Andrew Bartlett" <abartlet at samba.org> wrote: > On Mon, 2017-12-11 at 19:56 -0600, Taylor Hammerling via samba wrote: > > Good evening! > > > > I am having difficulty joining a Samba4 install to my current domain. > > What new