[Samba] Replication Problems After Changing FSMO DC
Dale Renton
drenton at gmail.com
Wed Jan 11 13:22:11 UTC 2023
> Does `samba-tool kcc` succeed?
[root at dc5 ~]# samba-tool drs kcc
Consistency check on dc5.ad.example.com successful.
> What about `samba-tool dbcheck`?
[root at dc5 ~]# samba-tool dbcheck
Checking 2566 objects
Checked 2566 objects (0 errors)
> Does `samba-tool visualize uptodateness -rS --utf8` show big numbers or
mostly
> zeros? That will tell you whether replication is actually succeeding,
despite
> the complaints.
it is trying to connect to the old DC, dc2
[root at dc5 ~]# samba-tool visualize uptodateness -rS --utf8
Failed to connect to ldap URL 'ldap://dc2.ad.example.com' - LDAP client
internal error: NT_STATUS_OBJECT_NAME_NOT_FOUND
Failed to connect to 'ldap://dc2.ad.example.com' with backend 'ldap':
LDAP client internal error: NT_STATUS_OBJECT_NAME_NOT_FOUND
Could not contact ldap://dc2.ad.example.com ((1, 'LDAP client internal
error: NT_STATUS_OBJECT_NAME_NOT_FOUND'))
> Are these DCs all in one site (in terms of AD objects, not necessarily
physically)?
dc1, dc2, dc3 and dc4 are in same site, dc5 and dc6 are in different sites
Thanks,
Dale
More information about the samba
mailing list