[Samba] ldapcmp issue

[mathias dufresne]

While I'm there speaking about ldapcmp, testing the 4.3.0rc4 I was facing
incoherency between the two DC regarding "servicePrincipalName", this
behaviour was happening on both domains I had.

This error was mine: I hadn't applied DNS fixes has shown in the following
link, the two DNS entries mentioned were missing.
https://wiki.samba.org/index.php/Check_and_fix_DNS_entries_on_DC_joins

Since these two DNS entries are added, modulo few seconds needed for
synchronisation, the ldapcmp issue disappeared on all DC of both domains.


2015-09-03 13:18 GMT+02:00 mathias dufresne <infractory at gmail.com>:

> 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 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
>>>
>>>
>>>
>> According to two microsoft webpages:
>>
>> https://msdn.microsoft.com/en-us/library/ms680921%28v=vs.85%29.aspx
>> https://msdn.microsoft.com/en-us/library/cc221004.aspx
>>
>> whenChanged is not replicated but if you examine ldapcmp.py (the bit of
>> samba-tool that compares AD databases) you will find this:
>>
>>                 # "whenChanged", # This is implicitly replicated
>>
>> So somebody went to all the trouble of adding it, but then commented it
>> out.
>>
>> Rowland
>>
>>
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>
>