3.0.25pre2 winbind woes

[SATOH Fumiyasu]

At Mon, 26 Mar 2007 17:59:54 +0200,
Aknin wrote:
> Not sure if this is for samba-technical or samba, but it pertains to a
> problem in 3.0.25preX that works in 3.0.24, so I hope I'm correct in
> sending it here.
> I'm using RID backend for a winbind deployment on a Solaris 10 server.
> 
> Since .25, I'm having trouble resolving the 'group' nss database, and
> am getting:
> [2007/03/26 17:36:24, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(563)
>   error converting unix gid to sid
> In my winbind log file. Resolving 'passwd' works OK. wbinfo -g works OK.

What do `wbinfo --group-info <ad-group-name>`,
`getent group`, `getent group <ad-group-name>` and
`getent group <ad-gid-number` say?

-- 
-- Name: SATOH Fumiyasu / fumiyas @ osstech.co.jp
-- Business Home: http://www.OSSTech.co.jp
-- Personal Home: http://www.SFO.jp/blog/

> I read the new winbind documentation and modified my smb.conf to
> include the following lines:
> [global]
> workgroup = AMBER
> netbios name = gandalf
> realm = AMBER
> security = ADS
> allow trusted domains = no
> idmap domains = AMBER
> idmap config AMBER: default = yes
> idmap config AMBER: backend = rid
> idmap config AMBER: range = 100000-999999
> idmap alloc config: range = 100000-999999
> 
> My old 3.0.24 smb.conf had the following lines, and worked correctly:
> [global]
> workgroup = AMBER
> netbios name = gandalf
> realm = AMBER
> security = ADS
> allow trusted domains = no
> idmap backend = rid:AMBER=100000-999999
> idmap uid = 100000-999999
> idmap gid = 100000-999999
> 
> On a hunch, I tried adding the 'idmap uid' and 'idmap gid' lines to
> the 3.0.25 configuration, it didn't work.
> 
> Tips? Bug against for 3.0.25?