similar to: winbind, nsswitch, AD and group membership caching?

Hi Rowland; thanks for your comment. Am Freitag, den 01.06.2018, 11:05 +0100 schrieb Rowland Penny via samba: > > Have the users logged in ? If not, then this is the expected > behaviour. > The users have logged in several times using ssh; does that suffice? As far as I can tell right now, it *looks* like this is computed just exactly once and never updated. Did a quick check

Hi Rowland; Am Freitag, den 01.06.2018, 11:42 +0100 schrieb Rowland Penny via samba: > > OK, how are you running the Unix domain members ? > Are you using the 'ad' or the 'rid' winbind backend ? > If you are using the 'ad' backend, have you given the groups a > gidNumber ? > Hmm, I only have these statements relating to winbind and idmap in my

On Fri, 01 Jun 2018 11:53:55 +0200 Kristian via samba <samba at lists.samba.org> wrote: > Folks; > > using samba+winbindd+pam+nsswitch to make several Linux servers > authenticate against an AD domain, I do have my setup mostly working > now: > > - AD users are able to ssh into the machine. > - wbinfo -g / -u does list all domain users. > - getent group / getent

On Fri, 01 Jun 2018 13:13:21 +0200 Kristian via samba <samba at lists.samba.org> wrote: > Hi Rowland; > > Am Freitag, den 01.06.2018, 11:42 +0100 schrieb Rowland Penny via > samba: > > > > OK, how are you running the Unix domain members ? > > Are you using the 'ad' or the 'rid' winbind backend ? > > If you are using the 'ad'

All, I wonder if someone can give me an idea what the file "netsamlogon_cache.tdb" contains... as I have noticed that I can be added to a group, and access will not appear on the Unix side for a good deal of time... but if I stop Winbind, remove the file "netsamlogon_cache.tdb", and re-start everything, it will then work. Can anyone tell me what the purpose of this file is,

I have 4 Samba 4.7.0 DCs. I have 3 clients using samba-winbind.x86_64 0:4.6.2-11.el7_4 with an identical configuration, which produce inconsistent user group membership for multiple users. I've tried using all 4 DCs explicitly (e.g., realm = dc01.mediture.dom), net cache flush and restarting winbind. I've also tested cloning a user and setting up the user as identical as possible:

El 2/9/18 a les 10:39, Rowland Penny via samba ha escrit: > All of this is just a sticking plaster on the problem, if winbind is > crashing on a regular basis, we need to know this and will need > level 10 logs, debug info etc. Without this info, it will never get > fixed. Meanwhile, I need my server to keep running, so the plaster looks fine. Besides, winbind isn't crashing,

El 2/9/18 a les 01:03, Luca Olivetti via samba ha escrit: > El 1/9/18 a les 03:03, Jamie Jackson via samba ha escrit: >> Hi folks, >> >> Every couple days any one of my project's 10 or so RHEL VMs can't be >> logged >> into with a domain account (active directory integration). Our admin goes >> in with a local account and restarts winbind to fix it.

El 11/10/19 a les 16:59, Luca Olivetti via samba ha escrit: > El 11/10/19 a les 16:12, Rowland penny via samba ha escrit: >> Try running this on a DC: >> >> samba-tool ldapcmp ldap://DC1 ldap://DC2 >> --filter='whenChanged,dc,DC,cn,CN,ou,OU' >> >> Replace 'DC1' and 'DC2' with your actual DC short hostnames >> >> It should

On 15/05/2020 14:28, Luca Olivetti via samba wrote: > > Well, then I don't know. I have a range 490-60000 for my domain and it > works. > I also have > > winbind nss info = rfc2307 > > but I don't know if it's relevant to your problem. Probably not, if you are running Samba >= 4.6.0 you can remove that line, it has been superceeded by: idmap config

On Mon, 3 Sep 2018 15:37:03 +0200 Luca Olivetti via samba <samba at lists.samba.org> wrote: > El 3/9/18 a les 15:23, Robert Marcano via samba ha escrit: > > >> > >> I run this cron job every minute. Winbind usually crashes once or > >> twice a day > >> > >> #!/bin/bash > >> getent group | grep -q 513 && exit 0 >

So the problem is that smbd session processes will forever cache the POSIX group memberships that the logged in user possesses. Consider a following example: *smb.conf: * [share_a] path = /mnt/a valid users = dude *ls -l /mnt:* drwxrwxr-x root group_a a */etc/group:* group_a:*:2000:user Now, a client mounts *share_a* as *dude* and has R/W access to it via his *group_a* group membership. Then,

I have succesfully migrated our users (~3900) from our Samba 3 DC/OpenLDAP, complete with passwords. I have some 300 + groups that I'm trying to get migrated to our Samba 4 AD. I can create the groups, but it looks from the domain-member's side that groups don't work as I expect them to. - Not all groups seems to be visible by using 'getent group'. It looks like groups

I've been running a NT4-style domain with a samba 3.x PDC using a LDAP back end and it's mostly worked very will for a long time. However since yesterday, clients are having problems with the domain. I saw that updates came out on all my systems - my PDC and BDC are ubuntu 12.04 LTS. The samba version there still seems to be 3.6x. A client with a problem that was working is Ubuntu

On 11/10/2019 14:58, Luca Olivetti via samba wrote: > El 10/10/19 a les 20:23, Luca Olivetti via samba ha escrit: >> Today I noticed something that has been going on for some weeks: >> >> I have 2 dc, (dc1 and dc2) both debian buster with the distro >> provided samba (4.9.5), recently upgraded from stretch. >> >> samba-tool drs showrepl on dc2 says >>

Hello, I'm trying to upgrade samba (TPTB are going to introduce win7 workstations) on my old server (mandrake 10.0) currently running 3.0.11. I setup a virtual machine to do some testing and I built rpms for 3.5.2 (apart from the other problems it has this one https://bugzilla.samba.org/show_bug.cgi?id=7263) then for 3.4.7 and finally for 3.3.12. Each one of them has problems, the most

Hi all, our setup is Samba 3.3 in W2K8 domain. It seems samba cache group memberships somewhere and after adding user to a new group it's necessary to relogin for that user to get new memberships. Is it possible to eliminate that nasty procedure? Thanks. -- Vladimir Vassiliev

Today I noticed something that has been going on for some weeks: I have 2 dc, (dc1 and dc2) both debian buster with the distro provided samba (4.9.5), recently upgraded from stretch. samba-tool drs showrepl on dc2 says DC=DomainDnsZones,DC=samba,DC=wetron,DC=es Default-First-Site-Name\DC1 via RPC DSA object GUID: 89812346-9037-43b0-86ab-c5052f55125d

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)

The 2023 X.Org Foundation elections are rapidly approaching. We will be forwarding the election schedule and nominating process to the membership shortly. Please note that only current members can vote in the upcoming election, and that the deadline for new memberships or renewals to vote in the upcoming election is 26 March 2023 at 23:59 UTC. If you are interested in joining the X.Org