solved [setlocalsid bug(?)]

[beast]

Got it.
Maximum SID is: S-1-5-21-4294967295-4294967295-4294967295 and all 
leading zero will be ignored.

Sorry for the noise.

--beast

beast wrote:
> Entry in ldap:
>
> dn: sambaDomainName=NTDOM,dc=example,dc=com
> objectClass: top
> objectClass: sambaDomain
> objectClass: sambaUnixIdPool
> sambaDomainName: NTDOM
> sambaSID: S-1-5-21-8356847619-717159689-892131381
> uidNumber: 1000
> gidNumber: 1000
>
>
> [root ]# net getlocalsid
> SID for domain SERVER is: S-1-5-21-4294967295-717159689-892131381
> [root ]# net getlocalsid ntdom
> SID for domain ntdom is: S-1-5-21-4294967295-717159689-892131381
>
> Note there is different in first entry after 1-5-21.
>
> [root ]# net setlocalsid S-1-5-21-8356847619-717159689-892131381
> [root ]# net getlocalsid
> SID for domain SERVER is: S-1-5-21-4294967295-717159689-892131381
>
> Still no changes.
>
> [root ]# net setlocalsid S-1-5-21-8356847619-717159689-892131999
> [root ]# net getlocalsid
> SID for domain SERVER is: S-1-5-21-4294967295-717159689-892131999
>
> Only last antry was changes.
> Any ideas?
>
> Version: samba-3.0.23d
>
>