Displaying 4 results from an estimated 4 matches for "recordsd".
Did you mean:
records
2018 Mar 12
2
failes replication ldap, error SPN
...ndows registers as CUMPUTER_NAME.example.com (computer name
in uppercase).
When synchronizing in the direction of Samba, 2 SPN entries appear
computer_name.example.com
CUMPUTER_NAME.example.com
And on the windows side, there is a replication error, since by the logic of Windows DC it is 2 identical recordsds
2018 Mar 12
2
failes replication ldap, error SPN
...> name
> > in uppercase).
> > When synchronizing in the direction of Samba, 2 SPN entries appear
> > computer_name.example.com
> > CUMPUTER_NAME.example.com
> > And on the windows side, there is a replication error, since by the logic of Windows DC it is 2 identical recordsds
>
> This is bug https://bugzilla.samba.org/show_bug.cgi?id=8929
>
> The last effort was in this thread:
>
> https://lists.samba.org/archive/samba-technical/2018-January/124878.html
>
> Andrew Bartlett
>
> --
> Andrew Bartlett http://samb...
2018 Mar 12
1
failes replication ldap, error SPN
...> > > When synchronizing in the direction of Samba, 2 SPN entries appear
> > > > computer_name.example.com
> > > > CUMPUTER_NAME.example.com
> > > > And on the windows side, there is a replication error, since by the logic of Windows DC it is 2 identical recordsds
> > >
> > > This is bug https://bugzilla.samba.org/show_bug.cgi?id=8929
> > >
> > > The last effort was in this thread:
> > >
> > > https://lists.samba.org/archive/samba-technical/2018-January/124878.html
> > >
> > > Andre...
2018 Mar 12
0
failes replication ldap, error SPN
...in uppercase).
> > > When synchronizing in the direction of Samba, 2 SPN entries appear
> > > computer_name.example.com
> > > CUMPUTER_NAME.example.com
> > > And on the windows side, there is a replication error, since by the logic of Windows DC it is 2 identical recordsds
> >
> > This is bug https://bugzilla.samba.org/show_bug.cgi?id=8929
> >
> > The last effort was in this thread:
> >
> > https://lists.samba.org/archive/samba-technical/2018-January/124878.html
> >
> > Andrew Bartlett
> >
> > --
>...