Upgrade issue with 3.0.21b->3.0.22

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerald (Jerry) Carter wrote:
> rpcclient $> lookupnames test
> test S-1-5-21-1924756635-1969438570-313073093-1001 (User: 1)
> rpcclient $> queryusergroups 1001
> group rid:[0x201] attr:[0x7]
> 
> rpcclient $> lookupsids S-1-5-21-1924756635-1969438570-313073093-513
> S-1-5-21-1924756635-1969438570-313073093-513 TEST1\None (2)
...

As a followup, this is what I got against a 2k & XP client
both in a domain and out of a domain.

rpcclient $> lookupsids S-1-5-21-3586763185-3851955248-3436744031-512
result was NT_STATUS_NONE_MAPPED

rpcclient $> lookupsids S-1-5-21-3586763185-3851955248-3436744031-513
S-1-5-21-3586763185-3851955248-3436744031-513 TANIS\None (2)

rpcclient $> lookupsids S-1-5-21-3586763185-3851955248-3436744031-514
result was NT_STATUS_NONE_MAPPED

The Users well know RID always resolves.





cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD63StIR7qMdg1EfYRAorSAKCivDa3M4ZSZ524LzsJWVE/7fN5zwCgp//D
RtUayRE4i8Xz4/BcWppP4zg=
=lCXG
-----END PGP SIGNATURE-----