similar to: NEG_CONN_CACHE questions

On Wednesday, 27 May 2020 16:21:31 PDT Jeremy Allison wrote: > On Wed, May 27, 2020 at 12:54:49PM -0700, Alexey A Nikitin via samba wrote: > > 3. Are the rules for how a DC gets put into NEG_CONN_CACHE documented anywhere besides the code itself, or wading through the code is my only option of getting to know the criteria? > > Only in the code I think, added in: > >

On Wed, May 27, 2020 at 12:54:49PM -0700, Alexey A Nikitin via samba wrote: > I've tried searching manuals and wiki, but I can't seem to find any specifics about NEG_CONN_CACHE entries other than 'idmap negative cache time' option in smb.conf, which refers to SID/UID/GID queries and not unavailable DCs. > Specifically the issue I've ran into recently is that with

On Thu, May 28, 2020 at 01:11:26PM -0700, Alexey A Nikitin wrote: > On Wednesday, 27 May 2020 16:21:31 PDT Jeremy Allison wrote: > > On Wed, May 27, 2020 at 12:54:49PM -0700, Alexey A Nikitin via samba wrote: > > > 3. Are the rules for how a DC gets put into NEG_CONN_CACHE documented anywhere besides the code itself, or wading through the code is my only option of getting to know

Hi, So I did some digging into the source code, and I think I've found the issue. Around line 120 of source3/libads/cldap.c: for (i=0; i<num_servers; i++) { NTSTATUS status; status = cldap_socket_init(state->cldap, NULL, /* local_addr */ state->servers[i], &state->cldap[i]); if (tevent_req_nterror(req, status)) { return tevent_req_post(req, ev);

Hi, This morning three of our FreeBSD-11.1-p11 servers with Samba 4.7.7 installations started to ignore ACL settings and reject user access to shares.  All three servers are members of DC running on Windows Server 2008R2.  Everything has been running ok for last few year.  I have been upgrading Samba and FreeBSD installations and on last Friday upgraded to the latest packages from

Hello, I have a RHEL 6.5 server that was configured to use Samba 3.6.9-167 to authenticate against a Windows 2008 R2 Active Directory domain. The authentication was working fine, but we needed users to log in to this RHEL box with their AD credentials and then access files stored on a Windows file server CIFS share globally mounted on the RHEL box. As such, we added the "cifsacl"

According to this bugzilla entry, bug 6870 has been fixed as of at least version 3.5: https://bugzilla.samba.org/show_bug.cgi?id=6870 However, I assert that it is present in 4.2.10, which ships with Debian Jessie. On my home network (IPv4 and IPv6), a box with Samba 4.2.10 with IPv6 disabled (via sysctl), will fail to contact a DC because the IPv6 connect fails immediately before the v4

On 06. aug. 2018 15:15, Oleg Cherkasov via samba wrote: > > This morning three of our FreeBSD-11.1-p11 servers with Samba 4.7.7 > installations started to ignore ACL settings and reject user access to > shares.  All three servers are members of DC running on Windows Server > 2008R2.  Everything has been running ok for last few year.  I have been > upgrading Samba and FreeBSD

On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote: > > > Hi, > > So I did some digging into the source code, and I think I've found the > issue. Around line 120 of source3/libads/cldap.c: > > for (i=0; i<num_servers; i++) { > NTSTATUS status; > > status = cldap_socket_init(state->cldap, > NULL, /* local_addr */

Hi there Yesterday at job we had a poltergeist with radius + winbind & samba in a linux box with authentication against an Active Directory (Windows 2012) The AD is formed by 3 windows servers. The linux box has a connection established against one of them thru port 445. Then this server downs and a bunch of messages like the following are shown in /var/log/messages May 19 16:40:59

On Friday, 3 April 2020 10:46:54 PDT Ralph Boehme wrote: > Am 4/1/20 um 11:09 PM schrieb Alexey A Nikitin via samba: > > Is there a way, preferrably without ugly hacks, to prevent this from happening on accident, by mistake? By this I mean ideally so that Winbind remains responsive even if someone mistakenly ran `wbinfo -u` or `wbinfo -g`, but limiting the result sets of these commands or

Hi, Recently I by mistake ran `wbinfo -u <username>` when I was actually intending to run `wbinfo -n <username>`. It ignored the <username> part and proceeded to fetch the usernames. On a small domain this shouldn't be too much of an issue, but I did it on a domain with thousands upon thousands of users. The result was that Winbind became for all intents and purposes

On Friday, 18 October 2019 12:24:46 PDT Ralph Boehme wrote: > You won't loose connectivity anyway. winbindd will just have to go > through DC lookup again in certain scenarios. This is exactly what I'd like to avoid. As I wrote in another message in this thread, it appears that switching DC shortly after domain join causes machine authentication failures until the new machine

On Thursday, 13 June 2019 09:18:25 PDT Goetz, Patrick G via samba wrote: > On 6/13/19 10:48 AM, Alexey A Nikitin via samba wrote: > > According to the MS docs SID=('S-'+version+identifier authority value+domain or computer identifier+RID). The SIDs that don't contain RID are the special cases of Machine SID, Domain SID, Service SID, and some predefined universal well-known

On Thursday, 13 June 2019 00:41:09 PDT Rowland penny via samba wrote: > On 13/06/2019 07:55, Alexey A Nikitin wrote: > > On Wednesday, 12 June 2019 13:07:56 PDT Rowland penny via samba wrote: > >>>> I think you mean 'RID' instead of 'SID' > >>> Yes, you're right. The Windows people seem to use the terms synonymously. > >> I cannot

Hi Everybody, We are integrating samba,kerberos and ldap samba-3.0.2a sun kerberos sun ldap all the three servers are on three different solaris machines. we were able to successfully integrate samba and ldap and works fine. When trying to bring in kerberos support , we changed the samba configuration file as follows interfaces = 131.183.20.96 bind interfaces only

Sorry for not being accurate in the original question. My testing environment is set to 20ms frames (PCM 16 8 1 to be precise). I have verified that all the frames that I feed to the AEC have the fixed size of 320 bytes. So this is why I am presuming that the the dumped files should be of equal size. The output signal is good and not distorted. It has echo, though. In a try to diagnose that I

On Friday, 18 October 2019 10:52:40 PDT Rowland penny via samba wrote: > On 18/10/2019 18:26, Alexey A Nikitin via samba wrote: > > Hi everyone, > > > > I have few questions about Winbind on AD DS domain member I'm having difficulty finding answers to in the docs on my own: > > * does Winbind remember the last DC it was connected to on shutdown, will it attempt to

On Wednesday, 5 February 2020 13:11:27 PST Rowland penny via samba wrote: > No, sorry, but your client needs to have the same time as the DC (+/- 5 > mins), so if you haven't installed an NTP client, I suggest you do. Speaking of which, any suggestions on what's the best way to found out which NTP servers the client should be tuned to in AD DS? From what I understand, they are not

SSSD has auto_private_groups setting which effectively automatically creates a private user group when getting users from AD that either don't have gidNumber set for them or have gidNumber set to be the same as uidNumber. Is there any option in Winbind that could help achieve a similar result? Say, I have a user 'alexey' with uidNumber 1174235, when I run `id alexey` I want to get