The Samba-Bugzilla – Bug 10736
Conflict handling of objects with the same sAMAccountName incomplete => NT_STATUS_INTERNAL_DB_CORRUPTION
Last modified: 2015-07-31 08:32:13 UTC
When an account with the same sAMAcountName is created on multiple servers.
We'll end with two account with the same name resulting in NT_STATUS_INTERNAL_DB_CORRUPTION on logon.
This can happen when a member server runs net ads join twice.
This explains that one sAMAccountName should be renamed to $duplicate-<RID>