Description Janis Meybohm 2013-01-10 11:26:18 CET

Created attachment 4969 [details]
debuglevel 15 log.smbd

This constellation was possible with UCS 3.0-2 and stopped working after the
3.1 update (same share on S3 memberserver (same domain) still works as
expected):


# smbclient -Ubutzer%univention //10.200.6.100/masteur 
Domain=[S4LISH] OS=[Unix] Server=[Samba 4.0.0rc6]
tree connect failed: NT_STATUS_NO_SUCH_GROUP

# testparm -vvv
[masteur]
        path = /masteur
        force group = forceme
        read only = No
        strict locking = No
        vfs objects = acl_xattr


# univention-s4search sAMAccountName=forceme | s4search-decode 
dn: CN=forceme,CN=Groups,DC=s4lish,DC=qa
objectClass: top
objectClass: group
cn: forceme
instanceType: 4
whenCreated: 20130109161227.0Z
whenChanged: 20130109161227.0Z
uSNCreated: 3873
name: forceme
objectGUID: 06803cc4-ecf2-4dee-bb1d-6753b3825fc4
objectSid: S-1-5-21-1738911416-233897720-2251434911-1121
sAMAccountName: forceme
sAMAccountType: 268435456
groupType: -2147483646
objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=s4lish,DC=qa
member: CN=butzer,CN=Users,DC=s4lish,DC=qa
uSNChanged: 3874
distinguishedName: CN=forceme,CN=Groups,DC=s4lish,DC=qa


Neither @S4LISH+forceme nor S-1-5-21-1738911416-233897720-2251434911-1121 are
working as "force group" argument.


It looks like samba is not able to detect the group type though the group
lookup seems fine:
---
[2013/01/10 10:45:19.980795, 10, pid=6201, effective(0, 0), real(0, 0)]
../source3/passdb/lookup_sid.c:77(lookup_name)
  lookup_name: S4LISH\forceme => domain=[S4LISH], name=[forceme]
[2013/01/10 10:45:19.980852, 10, pid=6201, effective(0, 0), real(0, 0)]
../source3/passdb/lookup_sid.c:78(lookup_name)
  lookup_name: flags = 0x077
...
...
...
[2013/01/10 10:45:19.984566, 10, pid=6201, effective(0, 0), real(0, 0)]
../source3/smbd/service.c:342(find_forced_group)
  forceme is a None, not a group
---


Find the full debuglevel 15 log attached.