Bug 4422 - Samba-3.0.24 (and previous) sometimes corrupts AD server name
Samba-3.0.24 (and previous) sometimes corrupts AD server name
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: winbind
x86 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2007-03-01 17:28 UTC by Jason Haar
Modified: 2007-03-01 17:28 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Jason Haar 2007-03-01 17:28:41 UTC
Hi there

A few times over the past 6 months I've noticed some of the Samba servers I've added to Win2K3-based AD domains via kerberos "net ads join" have ended up creating corrupted objects in Active Directory. Using "AD Users and Computers", I can see them showing up in Computer containers as follows:


That of course should have just been "server_name". I'm guessing about the NULL char - it actually shows up in the GUI as an unprintable char.

As I've said, I've seen a few of these in our Win2K3 AD over the past 6 months - and these corruptions have EXCLUSIVELY been associated with Samba servers. This corrupt entry tends to lead to that particular Samba server experiencing "weird" trust problems: e.g. it cannot authenticate users from Trusted domains - but is OK for users of the current forest.

I get the feeling that corruption looks like a buffer overflow? i.e. it meant to register just the hostname, but some other cruft got on for a free ride?

Unfortunately I have so far just being deleting these objects and re-adding the affected Samba servers to the domain, so I can't give any more detail on the matter. Of course if you are interested, I can make sure to get more next time it happens.