search for: dsgetncchanges

...alls out attempting to replicate CN=Configuration object X of Y. So I have been digging, digging, digging, and I found this in the log file of the DC the 2008R2 box is attempting to replicate from - Feb 1 16:52:42 larkin28 samba[18650]: ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges 2nd replication on DN CN=Configuration,DC=micore,DC=us older highwatermark (last_dn CN=414,CN=DisplaySpecifiers,CN=Configuration,DC=micore,DC=us) Feb 1 16:52:44 larkin28 samba[18650]: [2017/02/01 16:52:44.553389, 0] ../source4/rpc_server/drsuapi/getncchanges.c:1961(dcesrv_drsuapi_DsGetNCC...

...df-3657da7c4c98._msdcs.XXXX DC=DomainDnsZones,DC=XXX,DC=XXX,DC=XXX,DC=XX 37ba1799-307a-49ef-a6df-3657da7c4c98 = dcXXX-NEW Any  ideia ? Others DCs have message: May  9 15:36:34 dzeta samba[22387]: [2018/05/09 15:36:34.419248, 0] ../source4/rpc_server/drsuapi/getncchanges.c:1657(dcesrv_drsuapi_DsGetNCChanges) May  9 15:36:34 dzeta samba[22387]: ../source4/rpc_server/drsuapi/getncchanges.c:1657: DsGetNCChanges 2nd replication on different DN CN=Schema,CN=Configuration,DC=XX,DC=XXX,DC=XXX,DC=XX CN=Configuration,DC=XXX,DC=XXX,DC=XX,DC=XXX (last_dn CN=b04efd5a-4691-4e94-87d6-2a1a3cf3a08c,CN=NTDS Sett...

On Wed, 9 May 2018 11:02:45 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Thanks; > > but, i can use same name ou change name ? Upgrading in situ, then yes you can use the same data and to be honest, you should, but if you demote a DC, NEVER user the same name again (well not until you are 100% positive there are no traces of the old name in AD, probably at least 6

Hi, i have message in syslog, is problem ? :-/ May  9 01:21:48 dcXXX samba[16414]: [2018/05/09 01:21:48.965568,  0] ../source4/rpc_server/drsuapi/getncchanges.c:1657(dcesrv_drsuapi_DsGetNCChanges) May  9 01:21:48 dcXX samba[16414]: ../source4/rpc_server/drsuapi/getncchanges.c:1657: DsGetNCChanges 2nd replication on different DN CN=Schema,CN=Configuration,DC=XXX,DC=XXX,DC=com,DC=br CN=Configuration,DC=XXX,DC=XXX,DC=com,DC=br (last_dn CN=50c773dc-dfcf-4854-8a38-6595d70d3c9c\0ADEL:70d73d5...

...function ok(i thinks) but error in syslog... Regards; On 09-05-2018 01:25, Carlos wrote: > Hi, i have message in syslog, is problem ? :-/ > > > May  9 01:21:48 dcXXX samba[16414]: [2018/05/09 01:21:48.965568, 0] > ../source4/rpc_server/drsuapi/getncchanges.c:1657(dcesrv_drsuapi_DsGetNCChanges) > May  9 01:21:48 dcXX samba[16414]: > ../source4/rpc_server/drsuapi/getncchanges.c:1657: DsGetNCChanges 2nd > replication on different DN > CN=Schema,CN=Configuration,DC=XXX,DC=XXX,DC=com,DC=br > CN=Configuration,DC=XXX,DC=XXX,DC=com,DC=br (last_dn > CN=50c773dc-dfcf-4854-8...

...n other record, but i think this is the problem. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Carlos via samba > Verzonden: woensdag 9 mei 2018 14:32 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] DsGetNCChanges 2nd replication on different > > Thanks for answering! > > These lines have been placed in the wrong way for a long time > (servers > are already over 3 years old), at the time they did not have so much > "knowledge", then because of compatibility (and fear of st...

Thanks for answering! These lines have been placed in the wrong way for a long time (servers are already over 3 years old), at the time they did not have so much "knowledge", then because of compatibility (and fear of stopping something, I left the mesmeas) :-D I use this version because all other Dcs are in this, until I can not get a window of time to update, I'm keeping this

Thanks; but, i can use same name ou change name ? My Idea this moment... - Same name - Upgrade Dc to 4.7.X Regards On 09-05-2018 10:01, Rowland Penny via samba wrote: > On Wed, 9 May 2018 09:31:56 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >> Thanks for answering! >> >> These lines have been placed in the wrong way for a long time >>

...gt; ../source4/smbd/process_single.c:114(single_terminate) >>   single_terminate: reason[ldapsrv_call_loop: >> tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_RESET] >> [2017/10/12 08:38:57.969111,  0] >> ../source4/rpc_server/drsuapi/getncchanges.c:1961(dcesrv_drsuapi_DsGetNCChanges) >>   ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges >> 2nd replication on DN DC=samba,DC=company,DC=com older highwatermark >> (last_dn CN=Schema Admins,CN=Users,DC=samba,DC=company,DC=com) >> [2017/10/12 08:38:57.969762,  2] >> ../source4/rpc_se...

On Wed, 9 May 2018 09:31:56 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Thanks for answering! > > These lines have been placed in the wrong way for a long time > (servers are already over 3 years old), at the time they did not have > so much "knowledge", then because of compatibility (and fear of > stopping something, I left the mesmeas) :-D >

...] ../source4/rpc_server/drsuapi/getncchanges.c:1731(getncchanges_collect_objects) ../source4/rpc_server/drsuapi/getncchanges.c:1731: getncchanges on DC=ads,DC=dom,DC=be using filter (uSNChanged>=1) [2017/12/07 12:10:59.058507, 3] ../source4/rpc_server/drsuapi/getncchanges.c:2822(dcesrv_drsuapi_DsGetNCChanges) UpdateRefs on getncchanges for 8dcda717-56de-4ad9-a2e5-fa3d539bfa21 [2017/12/07 12:10:59.058543, 4] ../source4/rpc_server/drsuapi/updaterefs.c:209(drsuapi_UpdateRefs) DsReplicaUpdateRefs for host '8dcda717-56de-4ad9-a2e5-fa3d539bfa21._msdcs.ads.dom.be' with GUID 8dcda717-56de-4ad9-a2e5-...

...g that process makes samba startup succeed, replication work again, and samba funcion, until the next time this happens. But WHY is samba getting stuck in the first place? We are getting the following unusual in the logs on all three DCs: > ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges 2nd replication on DN DC=samba,DC=company,DC=com older highwatermark (last_dn CN=a_username,CN=Users,DC=samba,DC=company,DC=com) > ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges 2nd replication on DN DC=samba,DC=company,DC=com older highwatermark (last_dn CN=Schema Admins,CN...

On Wed, 9 May 2018 08:37:38 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > More information: > > samba -v (compilated) > > Version 4.4.4 > > Totla Dcs = 16 > > smb.conf: > > [global] >         workgroup = XXXX >         realm = XXXX.xxxxx.com.br >         netbios name = upsilon >         server role = active

...2017/10/12 08:38:57.958994, 3] ../source4/smbd/process_single.c:114(single_terminate) > single_terminate: reason[ldapsrv_call_loop: tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_RESET] > [2017/10/12 08:38:57.969111, 0] ../source4/rpc_server/drsuapi/getncchanges.c:1961(dcesrv_drsuapi_DsGetNCChanges) > ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges 2nd replication on DN DC=samba,DC=company,DC=com older highwatermark (last_dn CN=Schema Admins,CN=Users,DC=samba,DC=company,DC=com) > [2017/10/12 08:38:57.969762, 2] ../source4/rpc_server/drsuapi/getncchanges.c:1483(getnc...

...] ../source4/rpc_server/drsuapi/getncchanges.c:1731(getncchanges_collect_objects) ../source4/rpc_server/drsuapi/getncchanges.c:1731: getncchanges on DC=ads,DC=dom,DC=be using filter (uSNChanged>=1) [2017/12/07 12:10:59.058507, 3] ../source4/rpc_server/drsuapi/getncchanges.c:2822(dcesrv_drsuapi_DsGetNCChanges) UpdateRefs on getncchanges for 8dcda717-56de-4ad9-a2e5-fa3d539bfa21 [2017/12/07 12:10:59.058543, 4] ../source4/rpc_server/drsuapi/updaterefs.c:209(drsuapi_UpdateRefs) DsReplicaUpdateRefs for host '8dcda717-56de-4ad9-a2e5-fa3d539bfa21._msdcs.ads.dom.be' with GUID 8dcda717-56de-4ad9-a2e5-...

Hi James, Thanks for the quick reply. On 10/09/2017 08:52 PM, lingpanda101 via samba wrote: > You should be able to fix the 'replPropertyMetaData' errors with; > > samba-tool dbcheck --cross-ncs --fix --yes > 'fix_replmetadata_unsorted_attid' Yep, worked great! Fixed all of those replPropertyMetaData errors! :-) > The highwatermark doesn't necessarily

Hello, I upgrade the schema for our main ADDC and everything works properly, but the member DC (DC to an Existing AD) fails. Both servers are in version 4.10.2 Distro: Debian 9.8 *Main ADDC:* [2019/04/16 15:43:03.814846, 0] ../../source4/rpc_server/drsuapi/getncchanges.c:2919(dcesrv_drsuapi_DsGetNCChanges) ../../source4/rpc_server/drsuapi/getncchanges.c:2919: DsGetNCChanges 2nd replication on different DN DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br CN=Schema,CN=Configuration,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br (last_dn CN=ms-DS-cloudExtensionAttribute14,CN=Schema,CN=Configuration,DC=campus,DC=se...

.../drsuapi/getncchanges.c:1731(getncchanges_collect_objects)   ../source4/rpc_server/drsuapi/getncchanges.c:1731: getncchanges on DC=DomainDnsZones,DC=example,DC=com using filter (uSNChanged>=5275) [2018/06/13 16:13:11.413251,  3] ../source4/rpc_server/drsuapi/getncchanges.c:2822(dcesrv_drsuapi_DsGetNCChanges)   UpdateRefs on getncchanges for ebe5bcd2-1d05-493b-a482-00b5f91f0da1 [2018/06/13 16:13:11.414283,  2] ../source4/rpc_server/drsuapi/getncchanges.c:3006(dcesrv_drsuapi_DsGetNCChanges)   DsGetNCChanges with uSNChanged >= 5275 flags 0x80000074 on <GUID=29d6d5f5-1e87-427b-8e84-e978c1725c5a&...

...pi/getncchanges.c:1438(getncchanges_collect_objects) ../source4/rpc_server/drsuapi/getncchanges.c:1437: getncchanges on DC=DomainDnsZones,dc=xxxxx,dc=xxxxxxxx,dc=xx using filter (uSNChanged>=3696) [2017/05/08 10:39:14.056390, 3] ../source4/rpc_server/drsuapi/getncchanges.c:2018(dcesrv_drsuapi_DsGetNCChanges) UpdateRefs on getncchanges for xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [2017/05/08 10:39:14.057589, 2] ../source4/rpc_server/drsuapi/getncchanges.c:2125(dcesrv_drsuapi_DsGetNCChanges) DsGetNCChanges with uSNChanged >= 3696 flags 0x00000074 on <GUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx>;...

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