Bug 10736 - Conflict handling of objects with the same sAMAccountName incomplete => NT_STATUS_INTERNAL_DB_CORRUPTION
Summary: Conflict handling of objects with the same sAMAccountName incomplete => NT_ST...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.1.4
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Stefan Metzmacher
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-23 06:54 UTC by Stefan Metzmacher
Modified: 2021-02-06 00:25 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Metzmacher 2014-07-23 06:54:30 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.