similar to: winbind's libads/ldap_utils.c repeatedly says 'failed to reconnect (Timed out)'

I'm using winbind v3.0.22 on Debian Linux as a source for nss info. I have a group that was once known by winbind, but is no more: ------ beging shell except ------ # ls -ld ./ drwxrws--- 10 root $MND000-TT227MV5K24I 4096 2006-05-10 15:41 ./ # ------ end shell except ------ It must have been known, as I was the one who chgrp'ed the dir originally. I know what the group name is

Hello, This weekend Winbind crashes with: [2003/10/25 03:52:52, 2] libsmb/cliconnect.c:cli_session_setup_kerberos(493) Doing kerberos session setup [2003/10/25 03:54:31, 1] libads/ldap_utils.c:ads_do_search_retry(68) ads_search_retry: failed to reconnect (Timed out) [2003/10/25 03:54:31, 0] lib/fault.c:fault_report(36)

Okay, I started over from scratch with my samba server rebuild, but I am still getting some weird issues. Here are my config files of importance: --------------/etc/samba/smb.conf-------------------- # Samba Configuration File [global] workgroup = WAYNE realm = WAYNE.LOCAL server string = Samba Server security = ADS password server =

Hello, Thank You for prompt reply! As I stated, I don't have any issues that I'm aware of, but this file server is new in my infrastructure and I was worried that something is incorrect. I set minimal logging as a habit, and I bumped winbind recently to maybe see something that would help me solve this problem. What about this: ads_search_retry: failed to reconnect (No logon servers are

Packet send failed to 62.101.92.90(137) ERRNO=Network is unreachable [2004/05/03 10:27:45, 0] nmbd/nmbd_packets.c:reply_netbios_packet(975) Hi list, once again looking for some good advice. I apologize for the long email and for the mistakes I could have done. I'm running Samba 3.0.2-6.3E on White box linux 3.0 kernel 2.4.21-4.EL (clone of Red Hat EL 3.0), the environment is a Win 2k ADS

All, I fear I''ve become a pita with this, but windbind periodically dying on one of my machines is really starting to cause grief, and I have no idea what might be causing it, especially as the same config is used on several similar boxes which do not exhibit the problem. While I've posted the problem previously, I thought that maybe this latest log entry after winbind dies

Hello, I have an issue as stated in topic. My samba 4.8.3 file server, which is AD member frequently shows winbind errors (pasted below). From user perspective it seems to work fine, but I'm worried that I have something misconfigured and in the long run, I might run into some errors. My AD DC are running on samba 4.9.x (two of them), compiled from source with BIND as DNS backend (running on

I'm running Samba 3.0.4 on Red Hat Enterprise ES v3 (Update 2), utilizing ACLs on ext3. Yesterday I discovered that my backup application (Galaxy 5.0) doesn't back up ACLs and won't until the next release (sometime this fall). I figured that I'd do a "poor man's backup" of the ACLs by running "getfacl -R --absolute-names /shares > /root/acls" on a daily

Hi all, I am having a problem with winbind crashing on our profile server. It is running samba 3.0 alpha 23 on Red Hat 8.0. Here is an excerpt from the winbind log when it crashed: [2003/05/12 14:08:24, 3] libads/ldap.c:ads_connect(267) Connected to LDAP server 192.168.55.6 [2003/05/12 14:08:24, 3] libads/ldap.c:ads_server_info(1917) got ldap server name fozzy@CJNTECH, using bind path:

I have a samba server that has been running for quite a while, without any problems. Last week, out of the blue, everybody lost connections. I restarted winbind and samba and all was well. It happened again, and again all it took was a restart. It happened over the weekend then again on Monday, when I noticed winbind was gone and just restarted that. When i happened again today I looked into why.

On 16/07/2019 16:31, Kacper Wirski via samba wrote: > Hello, > > I have an issue as stated in topic. My samba 4.8.3 file server, which is AD > member frequently shows winbind errors (pasted below). From user > perspective it seems to work fine, but I'm worried that I have something > misconfigured and in the long run, I might run into some errors. > > My AD DC are

Hi, today we found the reason for a problem with Group-Memberships when running Samba as an ADS Domain Member. 1. Short Summary of the Environment =================================== = "old" Systems: - donald: Microsoft Windows 2000 as ADS Controller with 2 (daisy, tick) Backup Controller - 800 Users mostly replicated from Microsoft Exchange - 65 Groups - fix: Samba 2.2.8 on

I am running RH8 with the Samba-alpha3.23 from the RPMs. I was able to use Kerberos to add machine to a Windows AD domain without any problem and was able to get winbind to function properly. I was able to get group & user listing using wbinfo -g & -u, -t responds with proper information. I have run getent for passwords & groups. Since what appeared to be a successful getent, my

Hello, I'm using samba 3.0.4, compiled with Kerberos 1.3.1-7, in an W2k3 ADS environment and Kerberos and the Winbind daemon are used for authentication. While checking a winbindd.log file I saw the following PANIC internal error: winbindd.log ========= [2004/07/21 12:15:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(1032) user 'root' does not exist [2004/07/21 12:15:00, 1]

As of RC3 and RC4, I've noticed that winbindd's wb_getpwuid function is using the form <FQDN-domain><winbind-seperator><username>, and before, it was simply <NetBIOS-domain><winbind-seperator><username>. The net effect of what I'm seeing is that users which have a UNIX account locally on the samba box and also a domain account are being

Hi there, I'm using Samba 3.0 beta 3 on RH 9 (connecting to a Windows 2000 domain, as a member server) and I'm having trouble keeping samba running reliably. At random times it seems to stop recognising names from the domain. Restarting winbind fixes the problem, but then it occurs randomly again, usually once or twice a day. At least once it has fixed itself after being broken overnight

Hello everybody, I hope someone can help me with this or point me into the right direction since I am not being able to solve it since weeks. Since last year I was running Samba 4.1.6 on Ubuntu 14.04 LTS without issues as a active directory domain controller as well as member servers. Trouble started with the upgrade to Samba 4.3.8 (now 4.3.9). The ADS controller and most member servers are

suggestion for minor improvement of the smb.conf manpage in the context of the 'idmap backend' parameter. At least as of v3.0.22 the manpage says: Finally, using the idmap_ad module, the UID and GID can directly be retrieved from an Active Directory LDAP Server that supports an RFC2307 compliant LDAP schema. idmap_ad supports "Services for Unix"

Hi, I've got some problem with samba (v3.0.22) on a linux (RedHat 4 ES) running squid (2.5Stable6). My server has joined a WIndows Domain. My problem is that from time to time, and usually on rush hour, Squid runs out of authentication process and at the same time, winbind have also no more authentication process free (winbindd: Exceeding 200 client connections, no idle connection found).

It looks to me like the 'winbind nss info' parameter is designed to be a space-separated list of values. I say this because: 1) i gave it two values, separated by spaces, and testparm(1) did not complain; 2) the man page ( http://www.die.net/doc/linux/man/man5/smb.conf.5.html ) gives an example of two values. Assuming that's true, how do the multiple values work together? Is order