Bug 5149 - force user and force group render share inaccessible
Summary: force user and force group render share inaccessible
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: User/Group Accounts (show other bugs)
Version: 3.0.26a
Hardware: x64 Linux
: P3 major
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-17 05:04 UTC by António Oliveira
Modified: 2007-12-17 09:54 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description António Oliveira 2007-12-17 05:04:58 UTC
Hello everyone.

This is hapening with samba 3.0.26a, running on ubuntu 7.10n 64bit

If, on a share I activate either 'force user' or 'force group' the share becomes inaccessible. I can still see it, but am unable to enter it.

Here's an example smb.conf to reproduce this:
# < smb.conf >
[global]
   workgroup   = my group
   netbios name = houston
   server string = got-a-problem
   dns proxy = no
   interfaces = 127.0.0.0/8 eth0
   bind interfaces only = true
   log file = /var/log/samba/log.%m
   max log size = 1000
   syslog = 0
   panic action = /usr/share/samba/panic-action %d
   debug level = 2
   security = user
   null passwords = yes
   encrypt passwords = true
   passdb backend = tdbsam
   invalid users = root
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *passwd:*password\supdated\ssuccessfully* .
   socket options = TCP_NODELAY

[public]
   path = /example
   browseable = yes
   writable = yes
   create mask = 777
   directory mask = 777
   force user = to
   force group = to
# < /smb.conf >

/example is owned by to and has 777 permissions.
I have added and enables users to and ti.
If the smb.conf is as shown, none can enter the share. The same happens if I comment out only one of the force directives.
If I comment out *both* force directives, the share is accessible (RW) by both.

This is the log portion when the share is not working and I try to access them from some client:
--------8<----------------------
[2007/12/14 15:55:55, 2] auth/auth.c:check_ntlm_password(309)
  check_ntlm_password:  authentication for user [to] -> [to] -> [to] succeeded
[2007/12/14 15:55:55, 0] auth/auth_util.c:create_builtin_administrators(792)
  create_builtin_administrators: Failed to create Administrators
[2007/12/14 15:55:55, 2] auth/auth_util.c:create_local_nt_token(914)
  create_local_nt_token: Failed to create BUILTIN\Administrators group!
[2007/12/14 15:55:55, 0] auth/auth_util.c:create_builtin_users(758)
  create_builtin_users: Failed to create Users
[2007/12/14 15:55:55, 2] auth/auth_util.c:create_local_nt_token(941)
  create_local_nt_token: Failed to create BUILTIN\Users group!
[2007/12/14 15:55:55, 1] auth/auth_util.c:create_token_from_username(1110)
  sid_to_uid for to (S-1-5-21-133238273-2997305703-2950841162-3000) failed
--------------------8<--------------------------


Having those nasty directives commented out lets both users access the share. This is the log in that situation:
-------------8<----------------------
[2007/12/14 16:30:12, 2] auth/auth.c:check_ntlm_password(309)
  check_ntlm_password:  authentication for user [to] -> [to] -> [to] succeeded
[2007/12/14 16:30:12, 0] auth/auth_util.c:create_builtin_administrators(792)
  create_builtin_administrators: Failed to create Administrators
[2007/12/14 16:30:12, 2] auth/auth_util.c:create_local_nt_token(914)
  create_local_nt_token: Failed to create BUILTIN\Administrators group!
[2007/12/14 16:30:12, 0] auth/auth_util.c:create_builtin_users(758)
  create_builtin_users: Failed to create Users
[2007/12/14 16:30:12, 2] auth/auth_util.c:create_local_nt_token(941)
  create_local_nt_token: Failed to create BUILTIN\Users group!
[2007/12/14 16:30:12, 1] smbd/service.c:make_connection_snum(1033)
  withus-mobile1 (192.168.250.4) connect to service public initially as user to (uid=1000, gid=1000) (pid 8601)
---------------8<-------------------------

Best regards,
--to

P.S. thanks for such a great piece of software :-)
Comment 1 António Oliveira 2007-12-17 09:54:11 UTC
Nevermind, I decided to completely purge samba-common and samba from the server, and install them again. That seems to have fixed the prolem, although I still don't have a clue of what the problem wass (this was a fresh instalation of ubuntu server 64bit...)

Sorry for "bugging" you :-)

Cheers,
--to