search for: add_failed_connection_entri

thank you very much for your help...! i would be so happy if this works !!!! iv joined the domain scienceu : when i join the domain with smbpasswd, i type #./smbpasswd -j scienceu -r 11.1.9.100 -U administrateur and i have joined domain scienceu but if i type #./smbpasswd -j scienceu.org -r 11.1.9.100 -U administrateur i have the same answer here is my smb.conf : [global] workgroup

Hi, we have a winbind issue with Samba (Version 4.2.7-SerNet-RedHat-19.el6) on one of our servers. After a while (once a day) one of the winbind daemons causes a very high cpu load (100%). This load remains until we kill this process. This server is a member of a AD domain with several trusted domains. I think this happens because winbind has problems with one of the trusted domains (ALS2)

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

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

I have a suse 10.2 system, that runs the latest samba version, Suse provides for 10.2: 3.0.23d-6 After a long time I had to join that system to an AD domain. Unfortunately that did not work as expected. net ads join -U DE7B07K0@WW901.MYDOM.NET -d4 asks for a password, but then it fails with: ... [2007/08/23 18:24:14, 10] libsmb/namequery.c:remove_duplicate_addrs2(431)^M

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

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

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 'winbind max domain connections' set to 10 I saw Winbind had single active connection

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 */

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 List. I have successfully used winbindd, with squid to act as a reverse proxy for a webmail product. I initally tested and set up this system in our own LAN. This had the squid box, running winbindd, on the same LAN as our Win2k DC. Everything works fine. Now, once I came to install this system in the real world, I have run into some problems. I have compiled Samba 2.2.7a from source with the

Hello, I am trying to join my server to a Win2k AD domain. I have configured kerberos and can get a ticket but when I try to join the AD I get the error "Failed to join domain: No logon servers" as detailed below. I have searched the archives and google and followed some suggestions to get my files into the correct format but still have a problem. I am using Samba version 3.0.32-0.fc8

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

I've been checking the authentication with "wbinfo -a <username>%<password>", which is failing with the following error: plaintext password authentication failed error code was NT_STATUS_NO_SUCH_USER (0xc0000064) error messsage was: No such user Could not authenticate user <username>%<password> with plaintext password challenge/response password

I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10 client to the Samba domain without any issues. The