Comment 12 for bug 1736940

Hi Andreas,

I cannot show you the share definitions because I use the valid users "settings" which contains the real names of lots of my users, but I can show you the "Global Parameters".

# Global parameters
[global]
        workgroup = OURWORKGROUP
        server string = %h
        map to guest = Bad User
        obey pam restrictions = Yes
        pam password change = Yes
        passwd program = /usr/bin/passwd %u
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        unix extensions = No
        dns proxy = No
        usershare allow guests = Yes
        panic action = /usr/share/samba/panic-action %d
        idmap config * : backend = tdb
       invalid users = root

Could there be a mistake in the configuration of the "idmap config" directive in my smb.conf file?

From the official samba documentation, "this is the mapping mechanism to map POSIX user IDs and group ID to SIDs (Security Identifiers)

Is there something that might have changed from samba3 to samba4?

I mention this because at this stage I have a hard time if this bug is specific to my config or more general.

I appreciate your effort to troubleshoot this with me. I want to reinstall the complete OS and create all users over the Christmas break to see if I can reproduce the issues or not on the same version of Ubuntu, but I am unsure as to when exactly I might be able to do this.

Can we lower the priority of this bug and come back to it once I have had the chance to attempt to reproduce it by recreating all users from the scratch?

I feel the problem must be with the way that smbstatus accesses and validates the user database, but right now it is just a hunch because when I print the list of users with "pdbedit -L", they all appear correctly and everything else works great, including logging of "Share Access" by users.

THANK YOU VERY MUCH FOR YOUR HELP.