similar to: Upgrade to 4.7.0 Replication fails on DC2

> > 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. #

hi, I listed the 0ADEL entries with the command below and didn't find the object. # ldbsearch --cross-ncs --show-deleted -H /var/lib/samba/private/sam.ldb | grep "\0ADEL" I tried to delete using the command below, but it says it doesn't exist. # ldbdel -H /var/lib/samba/private/sam.ldb "<GUID=44b7fb44-1a88-42a4-854b-60bddd391577>" --show-deleted --relax delete

On 20/09/2020 00:30, Elias Pereira via samba wrote: > hi, > > I listed the 0ADEL entries with the command below and didn't find the > object. > # ldbsearch --cross-ncs --show-deleted -H /var/lib/samba/private/sam.ldb | > grep "\0ADEL" > > I tried to delete using the command below, but it says it doesn't exist. > # ldbdel -H

On 20/09/2020 15:31, Elias Pereira via samba wrote: >> But, the error with the replication still occurs. I thought the replication >> error was linked to the ghost entry error. >> # samba-tool drs replicate DC3 DC4 dc=campus,dc=company,dc=br --full-sync >> --sync-forced >> ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - >>

No errors occur, but still not replicating. It is not of all entries. For example, there are some users that the groups they are part, differ between the two DCs. In the link below there is a diff between groups of a specific user. # ldbsearch -H /var/lib/samba/private/sam.ldb "(samAccountName=125202)" memberOf | grep CN= | awk -F, '{ print $1 }'

hello, There is a group in my AD that has a user that does not exist. I can see it via RSAT. By running the command: samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes The following error occurs: Checking 10016 objects WARNING: no target object found for GUID component for one-way forward link member in object CN=ALUNOS,OU=GRUPOS,OU=CAMPUS,DC=mycompany,DC=net -

On Mon, 2 Oct 2017 09:59:47 +1300 Garming Sam via samba <samba at lists.samba.org> wrote: > Can you provide a bit more logs? At first glance, it doesn't seem > quite related to group memberships. > > > Cheers, > > Garming > > On 29/09/17 22:07, gizmo via samba wrote: > > Hallo, > > we have 5 ADDCs. All of them did run with sernet-samba 4.6.7.

Can you provide a bit more logs? At first glance, it doesn't seem quite related to group memberships. Cheers, Garming On 29/09/17 22:07, gizmo via samba wrote: > Hallo, > we have 5 ADDCs. All of them did run with sernet-samba 4.6.7. > I updated 4 of them to sernet-samba 4.7.0, one after the other, checked replication, everything seemed to be ok. > One day later a colleague

Hi Andrew, I did the requested update, but still have the same issue when doin samba-tool drs replicate : On the destination server : [2018/01/25 10:34:04.404627, 1] ../source4/dsdb/repl/replicated_objects.c:894(dsdb_replicated_objects_commit) Failed to apply records: replmd_delete: Failed to modify object CN=DMZRODC-0,CN=Deleted Objects,DC=ads,DC=XXX,DC=be in delete - attribute

> > The question has to be, why do you only have it on one DC ? I am also asking myself this question because the dc3 was the first one I provisioned. Ok. Somehow this was removed. Would it be possible to recreate this entry or the best thing to do is to change the roles to dc4 and provision another DC instead of dc3? On Mon, Sep 21, 2020 at 11:13 AM Rowland penny via samba < samba at

On 21/09/2020 15:23, Elias Pereira via samba wrote: >> The question has to be, why do you only have it on one DC ? > > I am also asking myself this question because the dc3 was the first one I > provisioned. > > Ok. Somehow this was removed. Would it be possible to recreate this entry > or the best thing to do is to change the roles to dc4 and provision another > DC

Regarding the groups, now it's all right. Another doubt is about this bydefaults entry. The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. Does it work that way or is there something wrong there? * Comparing [DOMAIN] context... * DN lists have different size: 5702 != 5703 * DNs found only in ldap://DC4:

On 21/09/2020 15:00, Elias Pereira via samba wrote: > Another doubt is about this bydefaults entry. > The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. > Does it work that way or is there something wrong there? Whilst there are a few attributes that do not replicate, all DN's should. > * Comparing [DOMAIN] context... > > * DN lists have different

Hallo, I encountered a similar problem. I created a test environment with two domain controllers (copy from a working environment). I tried to join a read-only domain controller. Unsuccessfully. Samba-tool fell with a error: .... added interface ens192 ip=192.168.59.5 bcast=192.168.59.255 netmask=255.255.255.0 resolve_lmhosts: Attempting lmhosts lookup for name dcg2.unn.global<0x20>

Hallo, we have 5 ADDCs. All of them did run with sernet-samba 4.6.7. I updated 4 of them to sernet-samba 4.7.0, one after the other, checked replication, everything seemed to be ok. One day later a colleague wanted to delete a lot of users with a powershell-script and since then the replication doesnt work anymore. (Im sure the script is not the problem, but it seemes like it triggered something)

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, We are facing to a replication issue on a couple of DC. We are now on 4.7.3 but we have been on 4.7.0 and 4.7.1 shortly We have a replication issue (samba-tool ldapcmp shows errors). But when trying to full sync we also get errors : [root at dc ~]# samba-tool drs replicate nas dc DC=ads,DC=dom,DC=be --full-sync Processing section "[netlogon]" Processing section

On 21/09/2020 00:35, Elias Pereira via samba wrote: > No errors occur, but still not replicating. It is not of all entries. > > For example, there are some users that the groups they are part, differ > between the two DCs. > > In the link below there is a diff between groups of a specific user. > # ldbsearch -H /var/lib/samba/private/sam.ldb "(samAccountName=125202)"

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