Bug 7272 - fetch_account_info fails if addmachinescript also sets up SAMAccount
fetch_account_info fails if addmachinescript also sets up SAMAccount
Status: NEW
Product: Samba 3.4
Classification: Unclassified
Component: User & Group Accounts
3.4.7
Other Windows XP
: P3 normal
: ---
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-21 15:20 UTC by Sven Strickroth
Modified: 2010-03-21 16:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Strickroth 2010-03-21 15:20:29 UTC
I'm using a addmachinescript which adds a new user for a machine account in ldap (with the unix uid depending on the PC name). The addmachinescript also adds/sets the objectClass sambaSamAccount from a template.

Iirc since an update from 3.3 to 3.4 domain joins of a windows 7 clients fail the first time when a machine account isn't already in ldap (in the logs i see: passdb/pdb_ldap.c:2197(ldapsam_add_sam_account) ldapsam_add_sam_account: User 'PC229$' already in the base, with samba attributes).

I tried to track this issue down and I suppose the commit <http://gitweb.samba.org/?p=samba.git;a=commitdiff;h=7a51d4e2c5097276f27b7c86f2d1d384a0dd545a> (the missing "/* try and find the possible unix account again */") is the reason for it.
Comment 1 Volker Lendecke 2010-03-21 15:57:07 UTC
If you are talking about failure to join a Samba-based DC, it is unlikely that the checkin you refer to is the reason. This code is only used during a vampire of an existing NT4 domain.

Is it possible that you are running nscd? If so, what happens if you kill it?

Volker
Comment 2 Sven Strickroth 2010-03-21 16:00:38 UTC
Yeah I'm running nscd, but this problem wasn't there before the update to samba 3.4.x.

Anyway I try to retest with nscd disabled in the next week.
Comment 3 Volker Lendecke 2010-03-21 16:10:58 UTC
It might be possible that your build did not properly detect libnscd.

Volker
Comment 4 Sven Strickroth 2010-03-21 16:27:24 UTC
I just rechecked: THe issue is still there with nscd disabled (and samba restarted afterwards).


Btw. I use nscd from glibc.