similar to: 4.1.12: ldapcmp differences on attribute 'whenChanged'

Hi Mourik, whenChanged was replicated in my test once I did replicate in both way, so it seems to me it is supposed to be replicated... Then the fact it is not always replicated seems to me an issue. Perhaps a bug report for these two issue (whenChanged not always replicated and ldapcmp hanging once DB is too much filled) would be the right way to proceed... Cheers, mat 2015-09-03 10:42

Thank you Rowland for these info. So no more issue with 4.2.3 and auto-replication : ) Cheers 2015-09-03 11:52 GMT+02:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > On 03/09/15 09:59, mathias dufresne wrote: > >> Hi Mourik, >> >> whenChanged was replicated in my test once I did replicate in both way, so >> it seems to me it is supposed to be

Hi Mathias, I am under the impression that whenChanged is one of the fields that do not replicate. Therefore we run ldapcmp like: samba-tool ldapcmp ldap://dcX ldap://dcY --filter=whenChanged Hope that helps, MJ On 09/01/2015 02:45 PM, mathias dufresne wrote: > Hi all, > > It seems "samba-tool ldapcmp" does not support too much items in Samba's > database. >

Hi all, It seems "samba-tool ldapcmp" does not support too much items in Samba's database. Playing for a while with DB I was never able to run ldapcmp successfully. So yesterday I installed a platform to fill piece by piece my two small DCs and to run ldapcmp. The process follows. Test platform: 2 DCs using Debian 8.1 "net install" with only system tools, up to date,

Hello Folks, I'm a Brazilian student. I'm doing some labs about SAMBA4 AD DC with 4 domain controllers (03 Linux Debian 8 x64 with SAMBA 4.3.1 installed by souce packeage and 01 Windows Server 2008 R2 Standard x64 to study for LPIC3 certification exam.) About the "samba-tool ldapcmp" (https://wiki.samba.org/index.php/Samba-tool_ldapcmp), in my lab, even applying the indicated

Hai, ? I've just upgrade samba on my DC's from 4.10.10 to 4.11.2. Which went fine offcourse ;-) but when i checking my replications i noticed the following. ? If people have problems upgrading, the steps to take are : ( Debian buster, samba upgrade 4.10=> 4.11 van-belle repo. ) # update 4.10 to 4.11 sed 's/410/411/g'? /etc/apt/sources.list.d/van-belle.list apt update apt

Hi, I have a domain with a single Windows 2003 DC running. Today I created a Samba4 DC (using 4.0.0 release) and asked it to join the existing domain as an additional controller. Replication of both the objects and dns entries appears to be working well, and the usual tests of adding a user to one and confirming it is available in the other is similarly working. However, the `ldapcmp` tool

Morning, On a DC: [root at BPCTASRVSDC003 ~]# samba-tool drs showrepl | grep failure 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0 consecutive failure(s). 0

On 23/06/16 17:49, Jason Waters wrote: > I did not get SUCCESS! > > root at DC01:/mnt# samba-tool ldapcmp ldap://dc01 ldap://pdc dnsdomain > > * Comparing [DNSDOMAIN] context... > > * Objects to be compared: 188 > > Comparing: > 'CN=Infrastructure,DC=DomainDnsZones,DC=fisherthompson,DC=local' > [ldap://dc01] >

I did not get SUCCESS! root at DC01:/mnt# samba-tool ldapcmp ldap://dc01 ldap://pdc dnsdomain * Comparing [DNSDOMAIN] context... * Objects to be compared: 188 Comparing: 'CN=Infrastructure,DC=DomainDnsZones,DC=fisherthompson,DC=local' [ldap://dc01] 'CN=Infrastructure,DC=DomainDnsZones,DC=fisherthompson,DC=local' [ldap://pdc] Attributes found only in ldap://dc01:

Problems with Secondary DC My scenario: DC1 = = SRV14=primary DC + DHCP Bind9 DC2 = SRV15=secondary DC + Bind9 Both running Samba 4.4.5. Through the Group Policy Management, when switching DC, when I try to connect to DC2, I get error message: "There was an error processing to collect data using this base domain controller. Change the base domain controller and try again." When

I have installed a secondary DC in my network, following the tutorial: https://wiki.samba.org/index.php/Join_a_domain_as_a_DC#Kerberos I have ran the following command: samba-tool domain join mydomain.com.br DC -Uadministrator --realm = mydomain.com --dns-backend = BIND_INTERNAL It seems that everything is OK. I have ran the following commands in both DC and the result was the same: ldbsearch

On 23/11/15 15:51, Matthew Delfino wrote: > > On 2015.11.23, at 8:32 AM, Rowland Penny <rowlandpenny241155 at gmail.com > <mailto:rowlandpenny241155 at gmail.com>> wrote: >> OK, try again, but this time, remove the <fSMORoleOwner> from the end >> of the command, this will dump the entire AD object, I am sure you >> will find that there is no

On Sun, 10 May 2015, Rowland Penny wrote: > Have you really got 19 reverse zones for your samba 4 active directory ? Yep :-) > Can you try running 'samba-tool ldapcmp ldap://<YOUR_FIRST_DC> ldap://<YOUR_SECOND_DC> Interesting. DC1 and DC2 have many differences; DC1 and DC3 are the same. Maybe I will demote DC2 and join it again. > Check if you actually have dns

Hai Mason,   I had a look at the debug output.   on 1) why around 15-16 second, that i really dont know. im trying to figure that out. on 2) if DNS is inconsistance, that everything is unrelayable. This is really the first the that needs fixing. then we look again at the replication.   The debug output still shows several messages about zones in flat files. I still do believe also that this

Running "samba-tool ldapcmp ldap://DC1 ldap://DC2 -Uadministrator" on our production system results in mismatches for items in the domain section: * Comparing [DOMAIN] context... * Objects to be compared: 625 Comparing: 'CN=AdminRole,OU=Group,OU=Postgres,DC=ourdomain' [ldap://DC1] 'CN=AdminRole,OU=Group,OU=Postgres,DC=ourdomain' [ldap://DC2] Difference in

Hello, Checking on the health of my DC's I ran samba-tool ldapcmp ldap://DC1 ldap://DC2 -Uadministrator This returned several failure results for both Domain and Configuration. Similar to the following Comparing: 'CN=Incoming Forest Trust Builders,CN=Builtin,DC=domain,DC=local' [ldap://dc1] 'CN=Incoming Forest Trust Builders,CN=Builtin,DC=domain,DC=local' [ldap://dc2]

> Turns out I made a dumb mistake. I did a kinit before ldapcmp, but > omitted the "-k 1" on the latter. When I do it correctly, all three DC's > are exactly the same. Phew. I thought kinit is not required on samba-tool ldapcmp I just tried _with_ kinit, and only saw the same differences on whenChanged. MJ

I am in the process of preparing to demote a couple of (hardware) aging domain controllers. At moment, I have four DC's running on my domain. When I "ldapcmp" between any of the DC's I get failures that appear to be simple "typos". Like these: root at dtdc07:~# samba-tool ldapcmp ldap://dtdc03 ldap://dtdc07 -Uadministrator >>>>> snipped for brevity

Hello I am running samba-tool ldapcmp, but is giving the following error. What may be happening? samba-tool ldapcmp ldap://dc-server1 ldap://dc-server2 -Uadministrator domain --filter=msDS-NcType,serverState Password for [UEL.BR\administrator]: * Comparing [DOMAIN] context... Failed search of base=DC=campus,DC=uel,DC=br ERROR(ldb): uncaught exception - LDAP client internal error: