On 21/09/2020 15:00, Elias Pereira via samba wrote:> Another doubt is about this bydefaults entry. > The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. > Does it work that way or is there something wrong there?Whilst there are a few attributes that do not replicate, all DN's should.> * Comparing [DOMAIN] context... > > * DN lists have different size: 5702 != 5703 > > * DNs found only in ldap://DC4: > > CN=BYDEFAULTS,CN=NETGROUP,CN=YPSERV30,CN=RPCSERVICES,CN=SYSTEM,DC=CAMPUS,DC=COMPANY,DC=BR > * Objects to be compared: 5702That DN is part of 'ypServ30.ldif', so if you provisioned with '--use-rfc2307' or added IDMU to a windows domain, you should have that CN in AD on all your DC's. The question has to be, why do you only have it on one DC ? Rowland
> > The question has to be, why do you only have it on one DC ?I am also asking myself this question because the dc3 was the first one I provisioned. Ok. Somehow this was removed. Would it be possible to recreate this entry or the best thing to do is to change the roles to dc4 and provision another DC instead of dc3? On Mon, Sep 21, 2020 at 11:13 AM Rowland penny via samba < samba at lists.samba.org> wrote:> On 21/09/2020 15:00, Elias Pereira via samba wrote: > > Another doubt is about this bydefaults entry. > > The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles > guy. > > Does it work that way or is there something wrong there? > Whilst there are a few attributes that do not replicate, all DN's should. > > * Comparing [DOMAIN] context... > > > > * DN lists have different size: 5702 != 5703 > > > > * DNs found only in ldap://DC4: > > > > > CN=BYDEFAULTS,CN=NETGROUP,CN=YPSERV30,CN=RPCSERVICES,CN=SYSTEM,DC=CAMPUS,DC=COMPANY,DC=BR > > * Objects to be compared: 5702 > > That DN is part of 'ypServ30.ldif', so if you provisioned with > '--use-rfc2307' or added IDMU to a windows domain, you should have that > CN in AD on all your DC's. > > The question has to be, why do you only have it on one DC ? > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- Elias Pereira
On 21/09/2020 15:23, Elias Pereira via samba wrote:>> The question has to be, why do you only have it on one DC ? > > I am also asking myself this question because the dc3 was the first one I > provisioned. > > Ok. Somehow this was removed. Would it be possible to recreate this entry > or the best thing to do is to change the roles to dc4 and provision another > DC instead of dc3? > > On Mon, Sep 21, 2020 at 11:13 AM Rowland penny via samba < > samba at lists.samba.org> wrote: > >> On 21/09/2020 15:00, Elias Pereira via samba wrote: >>> Another doubt is about this bydefaults entry. >>> The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles >> guy. >>> Does it work that way or is there something wrong there? >> Whilst there are a few attributes that do not replicate, all DN's should. >>> * Comparing [DOMAIN] context... >>> >>> * DN lists have different size: 5702 != 5703 >>> >>> * DNs found only in ldap://DC4: >>> >>> >> CN=BYDEFAULTS,CN=NETGROUP,CN=YPSERV30,CN=RPCSERVICES,CN=SYSTEM,DC=CAMPUS,DC=COMPANY,DC=BR >>> * Objects to be compared: 5702 >> That DN is part of 'ypServ30.ldif', so if you provisioned with >> '--use-rfc2307' or added IDMU to a windows domain, you should have that >> CN in AD on all your DC's. >> >> The question has to be, why do you only have it on one DC ? >> >> Rowland >> >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> >If you have one good DC, I would (if required) transfer/seize the FSMO roles to this and then demote the other DC and (after cleaning it) re-join it as a DC. If you try to create the DN on the DC where it is missing, you will get a collision if it tries to replicate to the other DC. Rowland