similar to: Modify replication topology?

Hello, I have been able to restore a backup, disabled samba initially, changed hostname, and then joined as a DC. It looks as if that was successful and some data was replicated. I had to manually update some DNS data to get it operational however. As a test whether user data (my major concern) was replicated, I disabled the old DCs and ran samba-tool user list, and the result was as expected.

Hi, It seems unlikely that the KCC is the cause of these issues. The KCC is only responsible for telling who to connect (and when) and doesn't actually affect any underlying network connectivity. Connectivity between the spokes should not be required and the communication between them is usually just some stale data. But none of that should affect either of these commands. Unless the DRS

Samba 4.5.1 (started with this version as well) I started with 3 domain controllers, DC1 and DC2 at the hub, and another, DC3 as a spoke. Everything was running smoothly with this config. No problems with 'samba-tool drs showrepl'. As soon as I started adding more 'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs showrepl' command. I believe

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 removed a DC using the DC removal tool mentioned in http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 as https://bugzilla.samba.org/show_bug.cgi?id=10734 prevents normal DC demotion. The DC was still all over in DNS, so I had to pick it out. Now replication between the remaining three DCs is broken [root at larkin26 ~]# samba-tool drs showrepl

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

On Sun, 2015-04-12 at 16:14 -0400, Adam Tauno Williams wrote: > I removed a DC using the DC removal tool mentioned in > http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 > as https://bugzilla.samba.org/show_bug.cgi?id=10734 prevents normal DC > demotion. > The DC was still all over in DNS, so I had to pick it out. > Now replication between

Hi, I get the following error when I am trying to check the replication status of my samba4 dc: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to nidy. failed - drsException: DRS connection to nidy. failed: (-1073741772, 'The object name is not found.') File "/usr/lib64/python2.7/site-packages/samba/netcmd/drs.py", line 39, in drsuapi_connect

Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: > On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: >> Hi, >> >> I get the following error when I am trying to check the replication >> status of my samba4 dc: >> >> ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to nidy. >> failed - drsException: DRS connection

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

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

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

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

Am 13.10.2016 um 16:28 schrieb lingpanda101 at gmail.com: > On 10/13/2016 10:19 AM, Ronny Forberger wrote: >> >> Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: >>> On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: >>>> Hi, >>>> >>>> I get the following error when I am trying to check the replication >>>>

Hi, I have been trying for days to solve this to no avail. I have taken over the IT responsibilities at a small school and am trying to get my head around their network and why they are having problems. They have 3 servers, Matthew, Genesis and Luke. Matthew is a Windows 2008 R2 server and holds all the FSMO roles but appears to be screwed up. It won't replicate with anything and randomly

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

I have two DC with Samba 4.2.1 and now I have set up a third DC with Samba 4.6.3. I have executed the command: samba-tool domain join empresa.com.br DC -U "EMPRESA\administrator" --dns-backend = SAMBA_INTERNAL And everything went well, however with the command: samba-tool drs showrepl The following message appears: root at dc3:/home/marcio# /usr/local/samba/bin/samba-tool drs

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