similar to: Strange problem samba+winbind+AD - transport endpoint is not connected

Displaying 20 results from an estimated 500 matches similar to: "Strange problem samba+winbind+AD - transport endpoint is not connected"

2010 Feb 03
0
winbind error?
Hello! i have some trouble with my samba setup (v3.4.5 or 3.3.10). the server is not responding (or very slow) for some minutes in log.winbindd-idmap i get: ---------------------------- [2010/02/03 04:14:27, 1] lib/util_tdb.c:521(tdb_wrap_log) tdb(/home/samba-server/samba/3.4.5/var/locks/mutex.tdb): tdb_lock failed on list 43 ltype=1 (Interrupted system call) [2010/02/03 04:14:27,
2009 Oct 22
0
Help needed with log.winbindd errors
Problem: Trying to finish creation of Samba 3.3.2 domain server on new 9.04 Ubuntu server. Did default Ubuntu installation of LAMP and Samba during installation. Successfully edited smb.conf, built users, server and resources visible in smbclient and in windows test workstation. Can login as different users, and join machines to the domain via windows. However, the whole system was INCREDIBLY
2015 Apr 15
1
wbinfo -u/-g/-n works, but not 'wbinfo -i' or 'id'
Quoting Adam Tauno Williams <awilliam at whitemice.org>: >>>> It should work, it sounds like a mis-configuration somewhere, can you >>>> post the smb.conf, /etc/nsswitch.conf, /etc/resolv.conf and >>>> /etc/krb5.conf from the member server. >>> "wbinfo -u" lists 415 lines >>> "getent passwd" returns 93 lines
2018 Aug 06
0
samba 4.7.7 shares on FreeBSD 11.1-p11 started to ignore ACL
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
2011 Jan 21
0
Can not set SPN errors (again)
Hello! I see where this came up on the list a few months and never really ws resolved. Someone resolved it by linking libnss_winbind ... But that's not my problem... I'm getting " Failed to join domain: failed to set machine spn: Operations error" when I do a net ads join. I've used this user account (me) to join many Samba 3.5.6 servers to the domain. Config file and
2013 Nov 15
0
NT_STATUS_NO_LOGON_SERVERS when winbindd under large traffic.
Hi list, Thanks in advanced. I have written a winbindd client software to do NTLM authentication by using WINBINDD_PAM_AUTH_CRAP message. that is to say, my winbindd client is similar to ntlm_auth, but with high performance. when I test it under large traffic, most of the time they all work well. and the transaction per second can reach more than 900. but sometimes, winbindd will return
2019 May 30
1
domain won't go online
Hi. I'm hoping for some advise/help. I have a domain that won't seem to go online: $ wbinfo --online-status BUILTIN : active connection MY-HOST : active connection FOO : no active connection The log for the domain repeats over and over again: [2019/05/30 09:34:10.259173, 3, pid=1606, effective(0, 0), real(0, 0), class=auth] ../../auth/ntlmssp/ntlmssp_sign.c:514(ntlmssp_sign_reset)
2018 May 24
0
Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
On Thu, 24 May 2018 09:32:56 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > I have 3 server: > > S.O. -  Debina 8 > > Winbind Version : 2:4.2.10+dfsg-0+deb8u3 > > Member Domain > > Samba Server : Ubuntu 14.04 with Samba 4.7.7 , are 18 Dcs > > --------------------- > > > In day 21/05 , the 3 server have same problema
2018 Dec 19
0
Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
Hey, But What's the reason of this error? On 05/25/2018 04:58 AM, Carlos via samba wrote: > Hi! > > Thanks  for answer! > > In future my plan is update, but this momento is no possible.. :-| > > But, same error, in same time, in 3 server, is very strange.... > > Regards; > > > On 24-05-2018 15:38, Rowland Penny via samba wrote: >> On Thu, 24 May
2018 May 24
2
Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
Hi! I have 3 server: S.O. -  Debina 8 Winbind Version : 2:4.2.10+dfsg-0+deb8u3 Member Domain Samba Server : Ubuntu 14.04 with Samba 4.7.7 , are 18 Dcs --------------------- In day 21/05 , the 3 server have same problema in same time, th problem resolved after 40 minutes.... Syslog server 1/2/3: May 21 08:14:12  winbindd[6718]: [2018/05/21 08:14:12.288624,  0]
2019 Nov 29
0
security=domain fails after upgr. to 4.9, winbind doesn't help
On 28/11/2019 22:32, Frank Steiner wrote: > Rowland penny via samba wrote: > >> So your server doesn't seem to be able to find winbindd, are you sure it >> is running ? >> >> What does this show: >> >> ps ax | grep '[w]inbind' >> >> What OS is this ? > > It's SuSE Linux Enterprise 15sp1. winbindd is definitely running, I
2020 Nov 23
2
domain member file server failed after upgrade from 4.11.14 to 4.13.2
Hi Rowland, Sorry to inform that none of thus packages solve my problem. But today, with some Tranquil.it helps, I have some news: - Upgrade from 4.11.14 -> 4.12.9 is OK - Upgrade from 4.12.9 -> 4.13.2 : problem is present with Tranquil.it AND Louis package - Fresh install + member join with 4.13.2 is OK (Centos AND Buster packages) Problem only occur when upgrading member to 4.13.2 with
2018 May 24
3
Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
Hi! Thanks  for answer! In future my plan is update, but this momento is no possible.. :-| But, same error, in same time, in 3 server, is very strange.... Regards; On 24-05-2018 15:38, Rowland Penny via samba wrote: > On Thu, 24 May 2018 09:32:56 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >> Hi! >> >> I have 3 server: >> >> S.O.
2009 Jul 10
4
Samba(3.2.12 and 3.4.0) - Winbind - trusted domains - Problem!
Good Morning! We got in some troubles using trusted domains and winbind. First i will tell you something about the network and samba configuration. For our SMB Environment we use Samba 3.2.12. We have three trusted domains. Our Samba Server uses LDAP as Backend. Most of the time it worked nice, but after some time Winbind loses User Entrys. On the windows side i can see "unknown user
2019 Mar 12
0
sometimes users fails to login
On Tue, 12 Mar 2019 11:32:46 +0100 Andrea Cucciarre' via samba <samba at lists.samba.org> wrote: > Hello, > > I have Samba 4.6 as AD domain member and sometime the users fails to > login, the issue disappear after some minutes. > I have enabled log leve 10 and I can see the following errors: > > 2019/03/12 09:20:32.280799,  5, pid=15466, effective(0, 0), real(0,
2019 Nov 28
2
security=domain fails after upgr. to 4.9, winbind doesn't help
Rowland penny via samba wrote: > So your server doesn't seem to be able to find winbindd, are you sure it > is running ? > > What does this show: > > ps ax | grep '[w]inbind' > > What OS is this ? It's SuSE Linux Enterprise 15sp1. winbindd is definitely running, I showed that in the first mail in the output of "rcwinbind status", there you can
2019 Feb 14
3
Losing connection to a DC
Hi, I am running samba/winbind 4.2.14 on Debian 8 which is joined to an Active Directory and would like to know if you have any idea with my issue. In my case, ntlm authentification is enabled in squid (proxy). Here is the problem that I am facing : "wbinfo -t" takes sometimes more than 30 secondes to display the result. For some reason, the server loses it's connection to the
2008 Sep 03
0
Winbind + Win2003 ADS + Trusted Domain Issue
Hello all, I am having an issue that I need help with and have been searching the web high and low for a solution. It involvs using winbind to authenticate Linux systems against a 2003 Active Directiry domain with a one-way trust. Here is the lay out. Domain "ABC" is the resource domain where the servers are located. Domain "XYZ" is the domain that the primary user accounts
2016 Aug 01
0
NT domain login no longer works after distro upgrade (samba 4.2.12 -> 4.3.11, 4.4.5)
Workstation  is member of NT domain, DC is samba 3.6.12. Was running Fedora 22 (samba 4.2.12), domain logins were working fine. Upgraded to Fedora 23 (samba 4.3.11) and domain logins no longer work: "Domain Controller unreachable, using cached credentials instead." Can connect to shares on the DC (e.g., with smbclient) without problem. Upgraded to samba 4.4.5 (from Fedora 24), issue
2009 May 06
0
problems with samba as pdc.
This is a really weird one. To the ( XP Pro ) client, I can join the domain, but can never log in. I've looked all over for a troubleshooting guide, but none have found the problem. Help!!! System: samba 3.3.4 on 64 bit debian lenny patched to current. Gigabit lan environment. When Joining the domain ( over an openvpn connection ), the client log shows: [2009/05/07 09:52:08, 0]