[Samba] Problems since upgrade from 3.0.23 to 3.0.25b

[John Drescher]

On 7/17/07, Jason Baker <jbaker at glastender.com> wrote:
>
>  This is saying that your user and group have confilcting sids because
> they should share the same base sid as everything else on the domain.
> To fix this you need to go through your ldap database and make sure
> that all sids have the same base.
>
> This is very strange. I added this user using the
> /etc/smbldap-tools/smbldap-useradd script. Which yielded a user SID of
> S-1-5-21-3568796296-2565465778-716510536-3404 but group sid
> S-1-5-21-1194936901-2368177035-684874509-513. If I check all my other users
> they have a user sid such as;
>
> S-1-5-21-1194936901-2368177035-684874509-XXXX
>
> and a group sid such as;
>
> S-1-5-21-1194936901-2368177035-684874509-XXXX
>
> If I run the command: net getlocalsid on the PDC I get:
>
> SID for domain ASTER is: S-1-5-21-3568796296-2565465778-716510536
>
> Shouldn't the PDC SID match the user and group SIDs?
>

net rpc info

should match. I am not sure about get local sid as it failed on my pdc.


So I deleted the user account, went into the LDAP Account Manager tool from
> a web browser, recreated the user, and now the user SID is correct:
> S-1-5-21-1194936901-2368177035-684874509-3408
> I then went back and tried to add a test user account using the
> /etc/smbldap-tools/smbldap-useradd script, and I get the following error:
>
> Could not find base dn, to get next uidNumber at
> /etc/smbldap-tools//smbldap_tools.pm line 1046, <DATA> line 283
>
> I'm not sure whats going on, everything worked fine until I upgraded to
> 3.0.25.
>

Are you sure your  smbldap tools conf files did not get updated somehow?

John