Bug 4057 - samba doesn't write own machine SID into secrets.tdb when configured as BDC
samba doesn't write own machine SID into secrets.tdb when configured as BDC
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: Domain Control
Other Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2006-08-26 13:58 UTC by Björn Jacke
Modified: 2009-04-04 08:03 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Björn Jacke 2006-08-26 13:58:14 UTC
when Samba is configured as BDC (for vampire for example) it doesn't write it's own machine SID into secrets.tdb when joining into the existing domain. One will have to join into the domain as member first (to make sambe write it's machine SID), then remove the machine from the domain and rejoin with BDC configuration.
I can't provide logs/sniffs atm, but I can reproduce this later and provide log files...
Comment 1 Gerald (Jerry) Carter 2006-08-26 14:06:31 UTC
That's why you run 'net rpc getsid' and the 'net setlocalsid'.
if you have a patch to remove the net for setloaclsid, 
I'll be glad to take it.
Comment 2 Björn Jacke 2006-08-26 14:26:48 UTC
I'm not talking about the domain sid, there is no own workstation account being written into secrets.tdb, you only get this in a domain member configuration.
Comment 3 Gerald (Jerry) Carter 2006-08-26 14:28:07 UTC
That's what the 'net setlocasid' does.  You get the 
domain SID (which sets itself in secrets.tdb) and then you
set the local machine SID to match the domain SID.
And then you join as a BDC.