similar to: winbind or netsamlogon_cache.tdb issue

Displaying 20 results from an estimated 100 matches similar to: "winbind or netsamlogon_cache.tdb issue"

2014 Jun 11
1
Expiry of entries in netsamlogon_cache.tdb
I think we're suffering from bug 8641 at the moment: https://bugzilla.samba.org/show_bug.cgi?id=8641 where the netsamlogon_cache.tdb entries are not expiring. We use AD groups for our (redhat) server auth, and also use server-side group auth for NFS (with the --manage-gids flag). So if a user is not in a group on the server, they're denied access to files as per group permissions.
2018 Jan 31
3
netsamlogon_cache.tdb & winbind.
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,
2005 May 04
2
winbind cache time?
Hello, according to 'man smb.conf': Default: winbind cache time = 300 I have not changed it in smb.conf, but when I remove some user from some group, command "groups DOMAIN+user" still shows that user belongs to the group even after a few hours after removing the user from that group. Any ideas why? samba 3.0.15pre2. Regards, Nerijus
2004 Aug 25
3
Samba as NT Domain Member via Winbind - After Upgrade users prompted for password for any shares
Hello, Apparently, I did a stupid thing today. I used apt-get on my Debian Woody system to upgrade my Samba packages from 3.0.2 to 3.0.6. Since doing so, all my users are prompted for a password when trying to access shares. Even just listing the IPC$, Windows XP systems prompt for user name and password. Windows 98 machines prompt for password. None are successful. I believe
2006 Jul 07
2
Problem with tdb files.
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
2019 Jul 18
2
getent passwd shows old name for renamed user
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
2020 Jul 15
2
Winbind group cache
Hi All, I have hit a snag with winbind's group caching on AD on one of our client's infrastructure. We have a client that is using AD groups to control ssh access to servers. The client is running a lot of different bugfix and build versions in the 3.6 branch all running on RHEL using rpm's. I have seen this issue cropping up in the ML from time to time and most of the solutions
2004 Oct 08
1
Trust between two samba domains
I have a problem with Samba: I want to make trust between two Samba domains. I have setup the trust on the DOMAINB server then on the Samba DOMAINA server "net rpc trustdom establish DOMAINB" I then get the following: Password: [entered password] Could not connect to server SERVERB [this is the PDC for the DOMAINB domain] Trust to domain DOMAINB established When I then try
2005 Aug 22
1
couldn't find service %u on 3.0.14a
Hi, I have an identical issue, hitting Win2K SP4, ever since upgrading to Debian Sarge. Here's an additional observation, and a workaround. We have roving profiles, and on any user logging in or out, Samba creates a profile directory called %u. That is, (for example) on logging out, instead of writing back to a directory called /home/samba_profiles/fred, it creates a new directory
2020 Jul 16
2
Winbind group cache
On Wed, 15 Jul 2020 at 15:29, Rowland penny via samba <samba at lists.samba.org> wrote: > On 15/07/2020 13:59, Ian Coetzee via samba wrote: > > Hi All, > > > > I have hit a snag with winbind's group caching on AD on one of our > client's > > infrastructure. > > > > We have a client that is using AD groups to control ssh access to >
2005 Jan 04
2
Problems on HP-UX 11i with 'user add script'
This one doesn't make any sense to me. What's worse, it seems to occasionally work and sometimes not. I am attempting to log into a domain (DOMA let's say) and I only have an account on DOMB. When DOMA's Samba PDC attempts to create a UNIX account for me, this is what happens: [2005/01/04 15:47:15, 3] auth/auth_util.c:smb_create_user(53) smb_create_user: Running the command
2006 Oct 12
1
Error message - what does it mean ?
Skipped content of type multipart/mixed
2009 Jan 19
0
Strange problems with ADS-groups and winbindd
Hello, we experience some strange problems with group memberships of ADS users using samba v3.2.4 on SLES-9. An upgrade to v3.2.7 didn't help. Changes to the membership of users in ADS universal groups doesn't take effect at all or take long time (1 day) to be seen on the linux side. For example the command "net" shows the following GIDs of a user: # for i in $(net ads
2017 May 31
1
Different primary group between 4.5.x and 4.6.x
On Wed, 31 May 2017 11:36:56 +0200 aluno3--- via samba <samba at lists.samba.org> wrote: > root at host:~# su DEV2+dev2user1000 > > DEV2+dev2user1000 at host:/$ whoami > DEV2+dev2user1000 > > DEV2+dev2user1000 at host:/$ echo "testpermissions" >> /testfile > > DEV2+dev2user1000 at host:/$ cat /testfile > testpermissions > >
2018 Oct 08
4
Persistent Winbind gid cache
Hello Samba team ! I'm network administrator in a french high school where I store my user/group ID using rfc2307. My client stations use Winbind to query rfc2307 attributes. Each new years, as all my students move to another class, almost all my user's gid are updated in AD. This gid is very important in my network because pam_mount mount only the share corresponding the to user's
2008 May 29
2
strange situation
smbd version 3.0.25b-0.4E.5 Our server was functioning very well for several months. Our SAN crapped out and the LUN the server was using was gone. Everything is back up except SAMBA is acting crazy. I am looking at the logs and I am getting /var/log/samba/winbindd.log winbindd: Exceeding 200 client connections, no idle connection found and ads_krb5_mk_req: krb5_get_credentials failed for
2008 Aug 18
4
samba + ads / user and group update-probem
Hello subscribers, we have a problem with keeping our group memberships up to date. If we e.g. remove a group membership from a user, we don?t see any change when trying "wbinfo -r j.doe" or "groups j.doe". Even after hours there ist no update. We also tried restarting smb, nmb, winbindd. Anyone has an idea? Some additional info: |samba/winbind-version: 3.2.0-17.fc9
2018 Oct 08
1
Persistent Winbind gid cache
Thank you very much for your help Rowland ! And sorry for my English, I'm french. Le lun. 8 oct. 2018 à 18:38, Rowland Penny via samba <samba at lists.samba.org> a écrit : > > On Mon, 8 Oct 2018 18:11:39 +0200 > Prunk Dump <prunkdump at gmail.com> wrote: > > > Hi ! > > > > I use samba 4.5 ( Debian stable ) and to get the primary group I want, >
2004 Oct 12
0
Authentication in trusded domain
Hi, I have two servers, servera (DOMAINA) and serverb (DOMAINB). I have made a trust between this domain. But I try logon computer from domaina as user for domainb, the log in serverb wrotes me that a authentication was succeded: [2004/10/12 17:19:19, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(620) SAM Logon (Network). Domain:[DOMAINB]. User:[bronasek@\\XP1] Requested Domain:[DOMAINB]
2018 Oct 18
2
NSS interface lists all domain users but gives error on single user
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