Bug 1949 - Windows Explorer always reports samba guest account as file owner
Windows Explorer always reports samba guest account as file owner
Product: Samba 3.0
Classification: Unclassified
Component: User/Group Accounts
Alpha OSF/1
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
: 1948 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2004-10-20 00:15 UTC by james.curedale
Modified: 2006-04-10 07:41 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description james.curedale 2004-10-20 00:15:50 UTC
smb.conf (slightly edited):

             client lanman auth = no
             client NTLMv2 auth = yes
             client plaintext auth = no
             client use spnego = no
             create mask = 0644
             encrypt passwords = yes
             guest account = smbguest
             kernel change notify = no
             log level = 1
             map archive = no
             name resolve order = wins hosts bcast
             netbios name = server1
             password server = *
             security = domain
             server signing = auto
             server string =
             socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=32768 
             strict locking = no
             username map = /usr/local/samba/lib/username.map
             utmp = yes
             wide links = no
             wins server = XXX.XXX.XXX.XXX
             workgroup = OURDOMAIN

             browseable = no
             path = /spare/share
             valid users = unixuser1 unixuser2 smbguest
             write list = unixuser2


!unixuser2    = domainuser_2 domainuser_3
!unixuser1    = domainuser_1
smbguest      = *

Reproducing the symptom:
- map share1 as any domain user
- in Windows Explorer (Win2k SP4), right click on any file in share1 and 
select 'Properties'
- click 'Security' tab
- file owner is ALWAYS shown as 'smbguest (SERVER1\unixfileowner)'
- file group is shown (correctly) as 'unixfilegroup (SERVER1\unixfilegroup)'

Further Information:

I have discovered that if 'unixfileowner = unixfileowner' is added to 
username.map the file owner is shown correctly as 'unixfileowner (SERVER1

Samba 2.2.8a displays the file owner correctly without modifying username.map.

After adding a few well placed debugs it appears that when Samba is populating 
the Name field of the Security tab the function 'local_lookup_name' calls the 
function 'map_username' with 'unixfileowner' as the argument. In the unmodified 
username.map file 'unixfileowner' can never match any RHS and consequently 
falls through to the wildcard entry.
Comment 1 Björn Jacke 2004-10-20 01:48:37 UTC
*** Bug 1948 has been marked as a duplicate of this bug. ***
Comment 2 Gerald (Jerry) Carter 2006-04-10 07:41:03 UTC
Domain users have to be fully qualified in all configuration files 
from 3.0.8 onwards. Details are described in the release notes.