similar to: WERR_INTERNAL_ERROR on samba-tool domain join

> You can ignore anything after 'Join failed', the join error has already > happened and it looks like a replication problem. Does the first > Nameserver in /etc/resolv.conf point to the first DC ? > How is /etc/hosts setup ? > > Rowland /etc/resolv.conf ----------------------------------------- # Generated by NetworkManager search privatedomain.com nameserver

On Thu, 2023-02-23 at 21:50 +0000, Rowland Penny via samba wrote: > I would normally bow to your expertise, but that error appears to be > coming from the clean up after the join failed. It deletes three > DN's > and then throws an error. > > > Or am I missing something While the print()ed messages after "Join failed" are cleanup, the exception is stored

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run samba-tool drs showrepl without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]

I am having some trouble joining a new samba4 server as a DC. I am pretty sure this stems from trying to use OpenChange and subsequently removing it. The new samba4 machine is running 4.0.7 and the existing is running 4.0.1. I am a little hesitant to do an in-place upgrade of the last working DC, so I wanted a replica to fall back on in case things go bad. Any help would be appreciated. On the

-------- Original-Nachricht -------- Betreff: Re: Fwd: dnsdomainzone replication failure Datum: Thu, 24 Jul 2014 13:32:56 +0200 Von: C.Kindler <kindc1 at gmail.com> An: Achim Gottinger <achim at ag-web.biz> Many thanks! I didnt thought about Microsoft Admin Tools :-) - Yes with this is much easier: Now the replication goes a little forward: in the logs there are now such

I have a very old domain i inherited that is running samba 4.5.6 but is on schema version 30. I added a windows 2003 DC and used the 2008r2 adprep.exe utility to upgrade the schema to version 47. To do so the 2003 server had to take the schema and infrastructure roles. I am now trying to use the repadmin utility to sync the schema back to samba to it is failing with the following: [2017/06/09

I joined the windows 2019 domain, where among the controllers there is a Samba DC version 4.8.5, and after that the replica stopped working windows servers <--> samba DC. Upgrading to version 4.9.4 did not help Errors: ``` фев 12 14:15:28 srv-dc01 samba[24637]: [2019/02/12 14:15:28.679872,  0] ../source4/dsdb/repl/replicated_objects.c:248(dsdb_repl_resolve_working_schema) фев 12

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run "samba-tool drs showrepl" without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]

Hello, I upgrade the schema for our main ADDC and everything works properly, but the member DC (DC to an Existing AD) fails. Both servers are in version 4.10.2 Distro: Debian 9.8 *Main ADDC:* [2019/04/16 15:43:03.814846, 0] ../../source4/rpc_server/drsuapi/getncchanges.c:2919(dcesrv_drsuapi_DsGetNCChanges) ../../source4/rpc_server/drsuapi/getncchanges.c:2919: DsGetNCChanges 2nd replication

OK, tried that. Kicked myself for not trying earlier... but it didn't work. In fact, the error has got worse. Now when I try to go from Genesis to Luke I get: sudo samba-tool drs replicate luke genesis DC=kcs,DC=local -Udomainadmin . . ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (1359, 'WERR_INTERNAL_ERROR')

Thanks Rowland and Garming for your help!! How about "another DC", or 'a second DC' ? Ok. Got it! :D Alternatively, re-joining the domain controller (or joining a new DC and > demoting the old one) probably works because I believe there is code to > handle this case. I re-joined (remove secrets.tdb and .lbd, copy idmap from existing DC...) and now works properly!

On 12.02.2019 11:16, Rowland Penny via samba wrote: > On Tue, 12 Feb 2019 14:28:44 +0500 > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > >> I joined the windows 2019 domain, where among the controllers there >> is a Samba DC version 4.8.5, and after that the replica stopped >> working windows servers <--> samba DC. Upgrading to

Hello, Thanks for the feedback Garming!!! 👍 On Wed, Apr 17, 2019 at 12:35 AM Garming Sam <garming at catalyst.net.nz> wrote: > Hi, > > While I think we have most of the 2012 schema problems under control > now, there's still quite a bit of work to get the functional level > things working. In order to actually raise the level, we still need to > implement a number of

On Tue, 12 Feb 2019 14:28:44 +0500 Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > I joined the windows 2019 domain, where among the controllers there > is a Samba DC version 4.8.5, and after that the replica stopped > working windows servers <--> samba DC. Upgrading to version 4.9.4 did > not help > > Errors: > > ``` > > фев 12

Hi, This is a known issue: https://bugzilla.samba.org/show_bug.cgi?id=12204 https://bugzilla.samba.org/show_bug.cgi?id=13713 There are currently patches in master to fix this issue. We could probably backport a patch to 4.10, but you'd have to rebuild Samba. Alternatively, re-joining the domain controller (or joining a new DC and demoting the old one) probably works because I believe there

Hi, While I think we have most of the 2012 schema problems under control now, there's still quite a bit of work to get the functional level things working. In order to actually raise the level, we still need to implement a number of features (mostly security). We're able to do some prep steps (so that things like Windows server 2012 R2 appear to join us but still use 2008 R2 FL) but

On Tue, 12 Feb 2019 12:21:29 +0100 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > On 12.02.2019 11:16, Rowland Penny via samba wrote: > > On Tue, 12 Feb 2019 14:28:44 +0500 > > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > > > >> I joined the windows 2019 domain, where among the controllers there >

Hi, Everything seems to be ok, but the following is happening now. When I put a new computer in the domain, it only appears in the "second DC" and does not replicate to the first DC. root at dc3:~# samba-tool computer list |grep MINT-TESTE root at dc3:~# root at dc4:~# samba-tool computer list |grep MINT-TESTE MINT-TESTE$ root at dc4:~# Any idea? On Wed, Apr 17, 2019 at 8:12 AM

Hello, If when joining the computer in the domain and at the moment who received the request was the "second DC", it should automatically synchronize with the "first DC", correct? On Wed, Apr 17, 2019 at 5:00 PM Elias Pereira <empbilly at gmail.com> wrote: > Hi, > > Everything seems to be ok, but the following is happening now. > > When I put a new

I hope this isn't too off topic, but I'd like a quick solution to a problem. I have a small network behind a NAT firewall (FreeBSD of course) and I'd like to block/redirect all traffic from the internal network to the local mail server (same box as firewall) in order to prevent direct smtp requests to the outside world (mainly virus/trokan programs). I think I have it right in this