similar to: Expiry of entries in netsamlogon_cache.tdb

Hello, i am using samba 3.0.9 (winbind in particular) on RHES server for a squid project : to authenticate users or check in they are member of some groups on AD W2K servers. It has been working fine for one year. Last week, we have defined new AD groups to use for this project. The problem that i am facing, is that for some users, the check to see if the user is in the group is working fine,

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,

W dniu 2019-07-18 o?21:39, ?ukasz Michalski via samba pisze: > W dniu 2019-07-18 o?21:22, Rowland penny via samba pisze: > >> On 18/07/2019 20:20, ?ukasz Michalski via samba wrote: >>> W dniu 2019-07-18 o?18:46, Rowland penny via samba pisze: >>> >>> I changed uid, sAMAccountName, msFU30Name from 'foo' to 'bar' using >>> ADUC

Hello Rowland Il giorno mer, 17/10/2018 alle 21.28 +0100, Rowland Penny via samba ha scritto: [...] > What does 'wbinfo -U 10182' return ? > The last number should be 2182 root at kubuntu-test:~# wbinfo -U 10182 S-1-5-21-1076504413-1754488879-1808648030-2182 root at kubuntu-test:~# wbinfo -n 'AGENZIA\lorenam' S-1-5-21-1076504413-1754488879-1808648030-2182 SID_USER (1) root

Hi All: I have problems with maintain tdb files. From samba doc, these files are = classified into persistent and temporary. From the man page of smbd, = these file are classified into persistent and not. However, there are = some files no need to backup but need to be persistent = (netsamlogon_cache.tdb), and some files need to backup but not need to = be persisten (registry.tdb). There are also

Hi, I wonder if there are any tools to simplify transition from TDB to RID on existing system in production. Long story short, by mistake one of our servers were configured with default idmap set to a range: idmap config * : backend = tdb idmap config * : range = 3000-7999 The server had joined domain and everything works just fine however I may need to fix user/group ids and make it like

Hi, I'm running Samba 3.6.6 on Ubuntu Quantal. I have a need to manually assign some of the UID mapping on a samba domain member file server. I have used tdbtool to add the correct mapping record to winbindd_idmap.tdb. However, I am at a loss as to how to force that change to "propagate" so as to show in the permissions structure of the file system and in the output of such

Background: FREEBSD 11.2 - SAMBA 4.10.15 Hello everyone, Good evening/afternoon/morning. I am trying to "reuse" the TDB database to my portal, where I want to store basically 3 information: IP address , Name, TimeStamp - where IP would be the KEY and "NAME,TIMESTAMP" would be the VALUE. I am using the tdbtool to insert/store data successfully (like the example below)

On Wed, Aug 29, 2018 at 03:36:23PM +0200, Peter Eriksson via samba wrote: > For what it’s worth you are not alone in seeing similar problems with Samba and gencache. > > Our site has some 110K users (university with staff & students (including former ones), and currently around 2000 active (SMB) clients connecting to 5 different Samba servers (around 400-500 clients per server).

On Mon, 2020-08-17 at 12:36 -0700, Jeremy Allison via samba wrote: > On Fri, Aug 14, 2020 at 08:33:33PM -0300, Suporte - KONNTROL via > samba wrote: > > Background: FREEBSD 11.2 - SAMBA 4.10.15 > > > > Hello everyone, > > Good evening/afternoon/morning. > > > > I am trying to "reuse" the TDB database to my portal, where I want > > to

Is it normal that the gencache.tdb should grow and grow “forever” and fill up with “RA/<hex>” posts? I’ve been investigating why our Samba 4.7.3 servers (happened with older version 4 servers too) would use such insane amounts of memory on our FreeBSD 11.1 servers (we see smbd processes using hundreds of megabytes of RAM and up to 5GB virtual memory). Anyway, one part that seems to use

Hi, I was having problem with the tdbsam backend in which a particular user got listed twice with pdbedit. (http://www.mail-archive.com/samba at lists.samba.org/msg109110.html) Without much hope in fixing it, I am planning to re-generating passdb.tdb on my PDC by: (1)exporting tdbsam to smbpasswd backend (2)delete passdb.tdb (3)re-import smbpasswd to tdbsam backend With the command `

I had to remove reference to some printer drivers via tdbtool on ntdrivers.tdb. 1. Do I need to restart smbd and nmbd to make these changes take effect? 2. If I restart smbd and nmbd will connected users get disconnected?

Hi Rowland, and many thanks for fast reply, When using --noexpiry, the userAccountControl is set to 66048, which disable expiry for password as well (in MS console, "password never expires" is now checked). This means that the password expiry (let say, every 6 month) will never popup again to the user, which is in my sense a wrong behaviour. Is there a way to change ONLY

Hi Rowland and list, I allow myself to give a UP to my message in case someone has an idea. Thanks, --Oliver Le 2023-05-24 15:55, Olivier BILHAUT via samba a ?crit : > Hi Rowland, and many thanks for fast reply, > > When using --noexpiry, > the userAccountControl is set to 66048, which disable expiry for > password as well (in MS console, "password never

Thanks for the answer Marcel, I did get them confused. Any ideas why then that my passwords don't seem to be expiring even well after 60 days and despite having the domain policy enforcing password expiry? Thanks. Regards. Neil Wilson. On Mon, Jan 12, 2015 at 12:46 PM, Marcel de Reuver <marcel at de.reuver.org> wrote: > Account expiry and password expiry are not the same....

On 18/07/2019 20:20, ?ukasz Michalski via samba wrote: > W dniu 2019-07-18 o?18:46, Rowland penny via samba pisze: >> On 18/07/2019 17:36, Kris Lou via samba wrote: >>> Might have something to do with this bug: >>> https://bugzilla.samba.org/show_bug.cgi?id=11482 >>> >>> You can find and make the relevant changes with ADSI Edit. >>>

Hi, we are using samba 3.0.24 as a printspooler for 80 network printers with a 500kB ntprinters.tdb for some years now. When we recently restarted samba we noticed that the ntprinters.tdb automatically shrinked to 24kB and printing was no longer possible. tdbdump of the original tdb-file is impossible too: "Failed to open ntprinters.tdb" The strange thing about this: we can solve

Hi All. I'm pleased to report that as of yesterday, OpenSSH -current now supports forced changes of expired passwords on most platforms, and bug #14 is now closed. Specifically, AIX's native authentication, BSD Authentication and shadow passwords with the expiry field are supported. The password is changed by exec'ing /usr/bin/passwd in the session. Interested parties should

https://bugzilla.mindrot.org/show_bug.cgi?id=2675 Bug ID: 2675 Summary: When adding certificates to ssh-agent, use expiry date as upper bound for lifetime Product: Portable OpenSSH Version: 7.4p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5