similar to: replication not done with missing DC?

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')

I have DC on samba 4.5.2 (pdc) Also I have additional DC on Win2008 R2. (bdc) pdc and bdc just host names When I trying to replicate samba to windows: pdc:~ # samba-tool drs replicate bdc pdc DC=tidykzn,DC=local Replicate from pdc to bdc was successful. pdc:~ # samba-tool drs replicate bdc pdc CN=Schema,CN=Configuration,DC=tidykzn,DC=local Replicate from pdc to bdc was successful. pdc:~ #

My samba4.11 server will only replicate one way: windows -> samba. Replication from samba -> windows fails. Details follow. I have a Samba 4.11 domain controller (fs1) that was added to an existing domain that had a Windows Server 2003R2 domain controller (fs) and Windows Small Business Server 2011 (sbs). fs1 is running on Debian 7.6 My issues seems similar to

I started with one dc, 'dc1', running samba v4.0.21, in subnet1. I successfully added two more dc's, 'dc2' and 'dc3', both running samba v4.0.24, both in subnet2. There are several firewalls between subnets 1 & 2. I continued to make firewall holes on behalf of msad after I added dc's 2 & 3. I.e. when they were added, there were patterns of communication

Hello, I set up a domain with two DCs (dns-backend is BIND9_DLZ) on a Debian 10 system. I used either the Debian-packages or the Packages from Louis (4.12.8). I created an Ansible-role to setup everything, starting from installing the packages over doing the provision/join up to change the settings for bind9. The first DC runs fine. After the reboot services are all present, allthe SRV Record for

Hi, When we try replicate domain tree from Win DC to Samba DC we have timeout error: ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (-1073741643, '{Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.') File

hi, After a "samba-tool drs showrepl" I saw that there had been an error in the replication of ForestDnsZones. I ran a "samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10" and the error below occurred. ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed

Hi, Many of these syncing problems were solved in Samba 4.7 (and probably a few more in 4.8). There were a number of unresolved locking issues that we uncovered as well as some inconsistencies with Windows replication. I would try join a DC with one of the latest Samba versions and see if your problems persist. Cheers, Garming On 21/06/18 21:35, Chris Lewis via samba wrote: > Hello, >

I'm using samba 4.0.3 (host samba01) and samba 4.0.5 (samba02) as DCs. samba01 already existed and I used samba-tool domain join to join samba02 to domain samba.x.y.z. This worked quiet well, but now replication fails: /usr/local/samba/bin/samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== ... DC=DomainDnsZones,DC=samba,DC=x,DC=y,DC=z Default-First-Site-Name\SAMBA01 via RPC

Hi together, Demoting from a Win-Server-Based Active Directory fails root at srvf01:~# samba-tool domain demote --server windc-server -UAdministrator Using srv15.lan.compumaster.de as partner server for the demotion Password for [COMPUMASTER\Administrator]: Desactivating inbound replication Asking partner server windc-server to synchronize from us Error while demoting, re-enabling inbound

> > Well, you wouldn't be able to delete it, how can you delete something that has already been deleted :-) Samba's ghosts... O.o :D Try running this: samba-tool domain tombstones expunge --tombstone-lifetime=1 Ok, this error was fixed!! Thanks Rowland!! But, the error with the replication still occurs. I thought the replication error was linked to the ghost entry error. #

Hello, I'm getting replication errors of this type on the Samba (version 4.1.4) server (name=Roquefort): ##### ############################# ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8418, 'WERR_DS_DRA_SCHEMA_MISMATCH') File

hi, After an update to our DC4, I started to notice the error "Failed to store repsFrom - Indexed and full searches both failed!" in the logs. root at dc4:~# tail -f /var/log/samba/log.samba Copyright Andrew Tridgell and the Samba Team 1992-2023 [2023/12/05 14:09:06.191978, 0] ../../lib/util/become_daemon.c:150(daemon_status) daemon_status: daemon 'samba' : Starting

Checking the databases against each other throws up pages and pages of errors. The two are completely out of sync now. What I have seen is that for no apparent reason, one of the servers suddenly decided it would sync with the Windows server, which appears to have updated the schema. Yesterday when I compared the databases on the two linux servers they only had a couple of errors, today, many

Hi, I have two Samba 4.12.3 DCs (eucalipto and aroeira) on a Debian Buster and a Windows 2008R2 DC (antares). Replication got broken: root at eucalipto:~# samba-tool drs replicate antares eucalipto DC=ad,DC=a1,DC=ind,DC=br ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8418, 'WERR_DS_DRA_SCHEMA_MISMATCH') ? File

When I start the replication from the other DC it works as you can see: ------- root at addc-01:~# samba-tool drs replicate rodc-01 addc-01 dc=example,dc=net Replicate from addc-01 to rodc-01 was successful. ------- Am 07.08.2018 um 15:26 schrieb Stefan Kania via samba: > Hello, > > I just start testing the setup of an RODC with 4.8.3 (I use the packages > from Louis). The join works

What does the WERR_BAD_NET_RESP means? I'm currently upgrading our DCs to 4.8.3 and I've noticed that the off-site DC has a sync problem of the CN=Configuration NC. The FSMO DC is still in the 4.5.5, but all other DCs, including the off-site are already on 4.8.3. Trying to sync the off-site DC with one of the updated DCs does not work either. The WERR_BAD_NET_RESP message already

Hi All, since Friday I get a surprising error, when I try to replicate my domain-controllers. This is new! It worked before in any direction without any failures... When I replicate from dc2 to dc1 this runs also, without any failures: root at dc1:~# samba-tool drs replicate dc1 dc2 DC=mydomain,DC=uni-frankfurt,DC=de Replicate from dc2 to dc1 was successful. Only when I try to replicate from

Hai, ? Im having the same problems as discribed here. https://lists.samba.org/archive/samba/2013-June/173981.html? samba4 install on debian with sernet samba. i did this about 10 times now, and this is the first time i have this. i've tried to update manualy. samba-tool drs replicate dc2 dc1 DC=INTERNAL,DC=DOMAIN,DC=TLD ? but results in : ERROR(<class

Greetings, I recently promoted a new DC in our existing domain. The existing domain consists of two domain controllers running Samba Version 4.2.0pre1-GIT-b505111 on Ubuntu 12.04 Server. The newly promoted DC is also running Ubuntu 12.04 server, but Samba Version 4.1.8. The promotion was successful and after a few tweaks to DNS, replication is working. It is however failing on some items and