similar to: samba ignores supplementary groups for acl

Hi, I'm running samba 3.4.5 on Centos (x86_64). The filesystem is ext3 with acl support. winbind works fine. Please see below. when I am logged in using ssh, I can list the files in a folder (/var/Share) for which the group "staff" has r-x permissions. The problem is I can't list the folder through samba: $ ssh cyberlab+kent at cladms003 Password: Linux cladms003

Hi, I'm running debian sarge with kernel 2.6.8-2-sparc64. I'm trying to use winbind to connect to a Windows 2000 server. I can use "net rpc join" to join the domain, but "wbinfo -u" returns an error. The trusted domains listed doesn't include the domain. Please see below: cladms003:~# net rpc join -U Administrator Password: Joined domain CYBERLAB. cladms003:~#

I am building xen-unstable (23860:a422e2a4451e) on Ubuntu 11.10. I noticed that the "make install" does not create lib entries in /usr/lib/. I see them only in /usr/lib64/. This is causing program like xenpaging to not find the xenctrl library (error while loading shared libraries: libxenctrl.so.4.2: cannot open shared object file: No such file or directory) Is this expected behavior or

Hi, We're using Samba 3.0.0 beta2 with a Windows 2003 domain controller at a client's site. OS: Vanilla Red Hat Linux 8.0 on i686 (no patches or updates). Samba compiled from source into RPM (makerpm.sh) and upgraded from version 2. --with-acl-support enabled. Filesystem: SGI XFS (kernel 2.4.21) from CVS. Using Winbind to provide ID mapping from Windows users and groups to Unix users

Is there a signal that can be sent to the smbd process, or some other method to tell smbd to reload the user's supplementary unix groups? We do not use Windows Domains and all access to files is controlled using Linux ACLs and supplementary groups defined using a web interface. Currently, when a new posix group is created and given access to a folder, the members of the group do not gain

Excuse me, i am french.... My SAMBA v3.0.13 (over a linux Redhat 7.3.1 With kernel 2.4.27-4) is configured with " security = ADS " to communicate with Active directory (2003 server). The problem : When i modify the group of a user in the Active directory, this modification is not completely taken into account in samba. In fact the orders "getent" and "wbinfo"

Greetings, We are having some rights issues on Samba 3.6.18 running on Slackware64 14.0 (the official Slackware Package). One of our users is having access issues and I believe I have traced the problem to the following entry in the log.smbd: Primary group is 0 and contains 0 supplementary groups Issuing the groups command for this user returns the 8 Linux groups in which the user has

You could try the setting. ntlm auth = mschapv2-and-ntlmv2-only >From man smb.conf The available settings are: · ntlmv1-permitted (alias yes) - Allow NTLMv1 and above for all clients. · ntlmv2-only (alias no) - Do not allow NTLMv1 to be used, but permit NTLMv2. · mschapv2-and-ntlmv2-only - Only allow NTLMv1 when the client

Dear, I am having a problem configuring Samba 4 domain member. The main server works only as AD and the second one will be for file sharing. Looking at the logs I see errors like: "UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups" Logs: https://pastebin.com/BR1W0X3E smb.conf: https://pastebin.com/B5Ve41KG Does anyone know what can it be? Thanks!

Hello! I thought this was a mistake, sorry. So I created the shared directories and defined which groups can access this directory and includes the users in the defined group. However, the user defined in the group cannot access the directory, gives access denied. Take a look at the settings, if you can give me a direction of where my error is. # smb.conf [SHARE] comment = SHARE path =

Rowland, thanks for listening. I am learning to use the list, this is the first time I use this feature, sorry for the inconvenience, I believe it is the last message that will be created as new. I changed my receive settings to be able to reply to messages individually. >From what you answered earlier, I have a main server with AD, running Samba 4, everything is configured and working. The

Sorry, I thought I had re-enabled delivery, but I had not. So trying to reply to Rowland Penny here: > On 14/05/2020 18:46, Orion Poplawski via samba wrote: >> All - >> >> I seem to be suffering from the common complaint that users loose >> supplementary group access after a while - in our case it seems to be >> connections left overnight. Restarting smb

On 5/15/20 8:22 AM, Rowland penny via samba wrote: > On 15/05/2020 14:56, Orion Poplawski wrote: >> On 5/15/20 12:56 AM, Rowland penny via samba wrote: >>> On 14/05/2020 21:59, Orion Poplawski via samba wrote: >>>> >>>> This configuration (dropping the username map script hack) seems to be >>>> working >>>> for us, does this seem

On 5/15/20 12:56 AM, Rowland penny via samba wrote: > On 14/05/2020 21:59, Orion Poplawski via samba wrote: >> Sorry, I thought I had re-enabled delivery, but I had not.? So trying to reply >> to Rowland Penny here: >> >>> On 14/05/2020 18:46, Orion Poplawski via samba wrote: >>>> All - >>>> >>>> ??? I seem to be suffering from the

On 5/15/20 12:56 AM, Rowland penny via samba wrote: > On 14/05/2020 21:59, Orion Poplawski via samba wrote: >> Sorry, I thought I had re-enabled delivery, but I had not.? So trying >> to reply >> to Rowland Penny here: >> >>> On 14/05/2020 18:46, Orion Poplawski via samba wrote: >>>> All - >>>> >>>> ??? I seem to be suffering

Greetings, We are having some rights issues on Samba 3.6.18 running on Slackware64 14.0 (the official Slackware Package). One of our users is having access issues and I believe I have traced the problem to the following entry in the log.smbd: Primary group is 0 and contains 0 supplementary groups Issuing the groups command for this user returns the 8 Linux groups in which the user has

I'm trying to solve this issue I'm having where using 'valid users = +unixgroup' just plain doesn't work. I can't find any /documented/ reason why this is so, but nevertheless, it seems to be the case. This is with samba 3.6.18, but seems to exist in all of 3.6.x and most or all of 3.5.x and perhaps earlier as well (see bug #6681). From what I can tell, the underlying

Hello, We have a rfs6000 wifi model controller from Extreme Network that has the ability to become a member of the AD. When we configure it according to Extreme support, the error "NT_STATUS_LOGIN_FAILURE" on the controller and in the samba logs shows the following errors. UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups [2018/03/19 17:26:25.986601, 5,

I haven't learned to use the list yet, sorry! :( See below the two smb.conf ### smb.conf - AD [global] netbios name = SRV-SAMBA realm = DOMINIO.LAN workgroup = DOMINIO dns forwarder = X.X.X.X server role = active directory domain controller idmap_ldb:use rfc2307 = yes ntlm auth = yes ldap server require strong auth = no tls enabled = no security = user vfs objects = acl_xattr map acl

I was wondering if any one else is having issues with supplementary groups not being recognized. It seems as if Samba is ignoring the sup.groups. I'm using RH9.0 on Intel with samba-3.0.0-2_rh9 and OpenLDAP 2.0.27. When I do a "id -a username" the user is in all the necessary groups but when accessing shares the users' primary GID is used only. For example, uid=1001(jgray)