samba - Jan 2017 - AD Replication issues due to lingering objects

We are trying to migrate away from out Windows 2008 R2 server to a Samba
based DC. At this point we have both the Windows server as a Samba server
as DC in the domain. After a while, we noticed that changes from the Samba
server were not replicated to the Windows machine. Further investigation
show that there are 2 lingering objects that prevent replication, and it
has been for quite a while.

The various procedures on the Microsoft site to remove the lingering
objects don't work against the Samba DC.
eg. repadmin /removelingeringobjects on the objects gives following error,
and no usefull information was found on Google:

DsReplicaVerifyObjectsW() failed with status 1745 (0x6d1):
    The procedure number is out of range.

I also disabled the Strict Replication Consistency on the Windows DC, so
that the object would be recreated and rereplicated, but that doesn't help
either. The eventlog says it's going to re-request the object from the
other DC as it doesn't have enough attribute information to recreate it,
but the object doesn't exists anymore on the other DC.

So basically, I'm looking for a solution that can solve this problem.

Can demoting and re-promoting the Samba DC solve this problem? If so, is it
as simple as running samba-tool domain demote on the samba DC and
afterwards running samba-tool domain join again?

Tom
-- 
Met vriendelijke groeten,
Tom Cannaerts


*Service and MaintenanceIntracto - digital agency*

Zavelheide 15 - 2200 Herentals
Tel: +32 14 28 29 29
www.intracto.com


Ben je tevreden over deze e-mail?

<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=5>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=4>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=3>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=2>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=1>

On Mon, 02 Jan 2017 11:30:44 +0000
Tom Cannaerts - INTRACTO via samba <samba at lists.samba.org> wrote:
> We are trying to migrate away from out Windows 2008 R2 server to a
> Samba based DC. At this point we have both the Windows server as a
> Samba server as DC in the domain. After a while, we noticed that
> changes from the Samba server were not replicated to the Windows
> machine. Further investigation show that there are 2 lingering
> objects that prevent replication, and it has been for quite a while.
> 
> The various procedures on the Microsoft site to remove the lingering
> objects don't work against the Samba DC.
> eg. repadmin /removelingeringobjects on the objects gives following
> error, and no usefull information was found on Google:
> 
> DsReplicaVerifyObjectsW() failed with status 1745 (0x6d1):
>     The procedure number is out of range.
> 
> I also disabled the Strict Replication Consistency on the Windows DC,
> so that the object would be recreated and rereplicated, but that
> doesn't help either. The eventlog says it's going to re-request the
> object from the other DC as it doesn't have enough attribute
> information to recreate it, but the object doesn't exists anymore on
> the other DC.
> 
> So basically, I'm looking for a solution that can solve this problem.
> 
> Can demoting and re-promoting the Samba DC solve this problem? If so,
> is it as simple as running samba-tool domain demote on the samba DC
> and afterwards running samba-tool domain join again?
> 
> Tom
What version of Samba are you using ?
'samba-tool dbcheck' has been improved lately, perhaps upgrading could
fix your problem.

Rowland

We're using the Debian 8 repository version, which is 4.2.14

Tom



Op ma 2 jan. 2017 om 13:15 schreef Rowland Penny via samba <
samba at lists.samba.org>:
> On Mon, 02 Jan 2017 11:30:44 +0000
> Tom Cannaerts - INTRACTO via samba <samba at lists.samba.org> wrote:
>
> > We are trying to migrate away from out Windows 2008 R2 server to a
> > Samba based DC. At this point we have both the Windows server as a
> > Samba server as DC in the domain. After a while, we noticed that
> > changes from the Samba server were not replicated to the Windows
> > machine. Further investigation show that there are 2 lingering
> > objects that prevent replication, and it has been for quite a while.
> >
> > The various procedures on the Microsoft site to remove the lingering
> > objects don't work against the Samba DC.
> > eg. repadmin /removelingeringobjects on the objects gives following
> > error, and no usefull information was found on Google:
> >
> > DsReplicaVerifyObjectsW() failed with status 1745 (0x6d1):
> >     The procedure number is out of range.
> >
> > I also disabled the Strict Replication Consistency on the Windows DC,
> > so that the object would be recreated and rereplicated, but that
> > doesn't help either. The eventlog says it's going to
re-request the
> > object from the other DC as it doesn't have enough attribute
> > information to recreate it, but the object doesn't exists anymore
on
> > the other DC.
> >
> > So basically, I'm looking for a solution that can solve this
problem.
> >
> > Can demoting and re-promoting the Samba DC solve this problem? If so,
> > is it as simple as running samba-tool domain demote on the samba DC
> > and afterwards running samba-tool domain join again?
> >
> > Tom
>
> What version of Samba are you using ?
> 'samba-tool dbcheck' has been improved lately, perhaps upgrading
could
> fix your problem.
>
> Rowland
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>
-- 
Met vriendelijke groeten,
Tom Cannaerts


*Service and MaintenanceIntracto - digital agency*

Zavelheide 15 - 2200 Herentals
Tel: +32 14 28 29 29
www.intracto.com


Ben je tevreden over deze e-mail?

<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=5>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=4>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=3>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=2>
<http://www.intracto.com/feedback?user=tom.cannaerts&response_code=1>