similar to: DsGetNCChanges 2nd replication on different

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 directory domain controller         #passdb backend = tdbsam         passdb backend = samba_dsdb         server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,

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

HI ! I demote dc "same" name and rename dc, but same IP adresss. But erro persiste... DC "new name" May  9 15:34:39 dcXXX-NEW samba[12278]:   UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT code 0xc0002105 for 37ba1799-307a-49ef-a6df-3657da7c4c98._msdcs.XXXX DC=DomainDnsZones,DC=XXX,DC=XXX,DC=XXX,DC=XX 37ba1799-307a-49ef-a6df-3657da7c4c98 = dcXXX-NEW Any  ideia ?

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

I am attempting to add a Windows 2008R2 DC to my S4 domain... and it always stalls 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

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

>> UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED / NT code If you use the RSAT tools ( dns administrator in windows ) Go to the A record, check the security tab, it needs SELF, i think thats missing Or point to an old server. Compair it to an other record, but i think this is the problem. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

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

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 >

On 10/12/2017 3:17 AM, mj wrote: > Hi all, James, > > After following James' suggestions fixing the several dbcheck errors, > and having observed things for a few days, I'd like to update this > issue, and hope for some new input again. :-) > > Summary: three DCs, all three running Version > 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports

Hi Andrew, Thank you for your answer. Don't have much more informations with these logs : ==> /var/log/samba/log.samba <== [2017/12/07 12:10:58.989255, 2] ../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

Hi all, James, After following James' suggestions fixing the several dbcheck errors, and having observed things for a few days, I'd like to update this issue, and hope for some new input again. :-) Summary: three DCs, all three running Version 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports no errors, except for two (supposedly innocent) dangling forward links

Hi Andrew. Any idea to solve this ? Thanks ----- Mail original ----- De: "Gaetan SLONGO via samba" <samba at lists.samba.org> À: "Andrew Bartlett" <abartlet at samba.org> Cc: samba at lists.samba.org Envoyé: Jeudi 7 Décembre 2017 12:16:27 Objet : Re: [Samba] Replication issue (maybe due to 4.7.0 bug?) Hi Andrew, Thank you for your answer.

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

Hi, Some time back I had written to the list about integrating Cisco ISE and facing errors with RPC login. When we actually integrated using ISE 2.4.0357 we noticed that Kerberos authentication is working like a charm. But MS-RPC authentication throws error. From the samba logs, we noticed that ISE workstation is able to negotiate the RPC ports switch to higher Dynamic RPC ports,

Hello. I've got a network of FreeBSD servers which traditionally hosted a classic domain. I upgraded some months ago, removing the old PDC and BDC and migrating to an AD DC controller in a jail. This is working fine with Samba 4.4.13. Now I'm trying to add a second DC, so I created a new jail on another physical server and went on with the setup, following: >

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 Sun, 2 Apr 2017 20:37:00 +0200 Karl Heinz Wichmann <wichmann-karl at web.de> wrote: > Hallo Rowland > > At the moment we use the internal samba dns. > > I have startet dcpromo and we get every second following message: > > [2017/04/02 20:26:29.712194, 2] > ../source4/rpc_server/drsuapi/getncchanges.c:1483(getncchanges_collect_objects) >

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

Hi all, We would appreciate some input here. Not sure where to look... We have three AD DCs, all running samba 4.5.10, and since a few days, the samba DCs are getting stuck regularly, at ramdon times. Happens to all three of them, randomly, and currently it is happening up to a few times per day..! Must be some common cause. For the rest, the systems appear fine, enough diskspace, nothing