search for: werr_ds_dra_bad_nc

Hi, during a demote of an online and working DC I receive this error dsreplicasync failed (8440 'werr_ds_dra_bad_nc') Any suggestion where could be the issue, server is not really demoted Server is samba 4.4.5 and other server that has fsmo roles is 4.10.7 Thanks

..., the error is: Deactivating inbound replication Asking partner server [someDC] to synchronize from us Error while demoting, re-enabling inbound replication ERROR(<type 'exceptions.RuntimeError'>): Error while sending a DsReplicaSync for partion DC=lan,DC=cimbal,DC=pt - (8440, 'WERR_DS_DRA_BAD_NC') File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/domain.py", line 786, in run drsuapiBind.DsReplicaSync(drsuapi_handle, 1, req1) I have two other DCs which seem to be working correctly. Replication and name resolution are working. All 7 FSMO roles have...

...urs self.drsuapi_handle, 1, req1) === output from “ samba-tool drs replicate dc2 dc1 OU=Users,OU=Company,DC=my,DC=company,DC=com -d9" === clipped . . . drsuapi_DsReplicaSync: struct drsuapi_DsReplicaSync out: struct drsuapi_DsReplicaSync result : WERR_DS_DRA_BAD_NC ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8440, 'WERR_DS_DRA_BAD_NC') File "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line 568, in run drs_utils.sendDsReplicaSync(server_bind, server_bin...

...Last success @ NTTIME(0) - ------------ Trying to replicate dc1 with dc2 - ------------ root at addc1:~# samba-tool drs replicate addc1 addc2 example.net ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8440, 'WERR_DS_DRA_BAD_NC') File "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line 345, in run drs_utils.sendDsReplicaSync(self.drsuapi, self.drsuapi_handle, source_dsa_guid, NC, req_options) File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", line 83, in sendDsReplicaSync...

...ting inbound replication > Asking partner server [someDC] to synchronize from us > Error while demoting, re-enabling inbound replication > ERROR(<type 'exceptions.RuntimeError'>): Error while sending a > DsReplicaSync for partion DC=lan,DC=cimbal,DC=pt - (8440, > 'WERR_DS_DRA_BAD_NC') > File > "/usr/local/samba/lib64/python2.7/site > -packages/samba/netcmd/domain.py", > line 786, in run > drsuapiBind.DsReplicaSync(drsuapi_handle, 1, req1) > > > I have two other DCs which seem to be working correctly. Replication > and >...

...cal to synchronize from usError while replicating out last local changes from 'DC=domain,DC=local' for demotion, re-enabling inbound replicationERROR(<type 'exceptions.RuntimeError'>): Error while sending a DsReplicaSync for partition 'DC=domain,DC=local' - (8440, 'WERR_DS_DRA_BAD_NC')  File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/domain.py", line 786, in run    drsuapiBind.DsReplicaSync(drsuapi_handle, 1, req1) There is a bug registered for the 4.4.2 version of Samba, which has a patch to fix the problem, but the patch does not work for the 4...

On Sun, 14 Aug 2016 19:18:41 +0100 Alex Crow via samba <samba at lists.samba.org> wrote: > > > > > Ok, lets just run through this: > > You have an NT4-style PDC > Correct. > > You classicupgrade this to a DC > Yes, with BIND9_DLZ DNS backend. > > > You join another computer as a DC > > > > At this point, have you checked that all DNS

...vating inbound replication Asking partner server dc1.bales.lan to synchronize from us Error while demoting, re-enabling inbound replication ERROR(<type 'exceptions.RuntimeError'>): Error while sending a DsReplicaSync for partion CN=Schema,CN=Configuration,DC=bales,DC=lan - (8440, 'WERR_DS_DRA_BAD_NC') File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/domain.py", line 786, in run drsuapiBind.DsReplicaSync(drsuapi_handle, 1, req1 > >>> Are you turning Bind9 off on the remaining DC at this point ? >> After this point I've shut down the o...

...E(0) > - ------------ > > Trying to replicate dc1 with dc2 > - ------------ > root at addc1:~# samba-tool drs replicate addc1 addc2 example.net > ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - > drsException: DsReplicaSync failed (8440, 'WERR_DS_DRA_BAD_NC') > File "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line > 345, in run > drs_utils.sendDsReplicaSync(self.drsuapi, self.drsuapi_handle, > source_dsa_guid, NC, req_options) > File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", li...

...tsent: lmhost entry: 10.0.1.100 DC01 getlmhostsent: lmhost entry: 10.0.1.135 W2008R2 Received smb_krb5 packet of length 1258 Received smb_krb5 packet of length 1280 ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8440, 'WERR_DS_DRA_BAD_NC') File "/usr/local/samba-4.4.5/lib/python2.7/site-packages/samba/netcmd/drs.py", line 350, in run drs_utils.sendDsReplicaSync(self.drsuapi, self.drsuapi_handle, source_dsa_guid, NC, req_options) File "/usr/local/samba-4.4.5/lib/python2.7/site-packages/samba/drs_utils.p...

...n > Asking partner server dc1.bales.lan to synchronize from us > Error while demoting, re-enabling inbound replication > ERROR(<type 'exceptions.RuntimeError'>): Error while sending a > DsReplicaSync for partion CN=Schema,CN=Configuration,DC=bales,DC=lan > - (8440, 'WERR_DS_DRA_BAD_NC') File > "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/domain.py", > line 786, in run drsuapiBind.DsReplicaSync(drsuapi_handle, 1, req1 > > > > > > >>> Are you turning Bind9 off on the remaining DC at this point ? > >> Aft...

...licate works fine for the base > partition and > Configuration, but replicating ForestDnsZones or DomainDnsZones both > fail with: > > > ERROR(<class 'samba.drs_utils.drsException'>): > DsReplicaSync failed - drsException: DsReplicaSync failed > (8440, 'WERR_DS_DRA_BAD_NC') > > File > "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line > 368, in run > > drs_utils.sendDsReplicaSync(server_bind, > server_bind_handle, source_dsa_guid, NC, req_options) > > File > "/usr/lib/python2.7/dist-packages/samb...

Once again, something with Samba thirty bazillion components broke. Once again, my choices for logging are "nothing" or "15 MB/s spread of ten different files, because 'client authentication failed' totally needs to be lower priority than malloc debug info". Once again, none of these messages is actually able to convey what broke, where, why. Why is it impossible for