similar to: Solaris 11.1 + Samba 3.6.6 + ads + getent group - a bug, perhaps?

Hi we have a Samba-Winbind 3.5.10 and i have a big quantity of errors in logs : [2012/09/24 16:01:29.248286, 1] winbindd/winbindd_ads.c:728(lookup_usergroups_memberof) lookup_usergroups_memberof ads_search member=CN=TESTDD,OU=Villeurbanne,OU=ExEA,DC=ELIOTT,DC=fr: Out of memory [2012/09/24 16:03:38.498533, 1] libads/ldap_utils.c:323(ads_ranged_search_internal) could not pull first

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, 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

My samba machine authenticates logins from our AD domain and stores SID->UID mappings with idmap_ldap. Every couple of days winbind crashes, though not regularly. It's not linked to new users logging into our machine, though it might be new users being added to the domain (I don't control the domain). The core dump seems to indicate an LDAP problem. I found some similar

Hello everyone,   any ideas on why a newly installed domain member (w2k8 domain) might seem to work fine in every test (wbinfo -g, wbinfo -t, getent group, wbinfo -n username, getent passwd user, share-access.., ) but only enumeration of users with wbinfo -u and getent passwd fail? wbinfo -u just returns without any output and getent passwd just shows the default centos7 users.   Even with

Originally filed by Robert LeBlanc as Debian Bug # 652679 - <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652679> <Quote> Package: winbind Version: 2:3.6.1-3 Severity: important Dear Maintainer, After upgrading to 3.6.1 I am no longer able to login to Debian using my Active Directory account. 'winbind -u', 'winbind -g', 'winbind -t' and many others work

Hello all. Seems I can't find the root cause of $subj. When I store a file on my "home", it gets chmodded ugo+x ... My smb.conf is: -8<-- [global] workgroup = PERSONALE realm = PERSONALE.EXAMPLE.COM server string = Local shares netbios name = STR00160-SAMBA security = ADS encrypt passwords = true password server =

I just upgraded our system here to 3.0.0 from RC4 last night. As usual I built an RPM from the source RPM after adding --with-acl-support to the specfile. I found that unlike previous RCs, RPM would not upgrade to 3.0.0 using -Fvh. In the end I removed RC4 and then installed 3.0.0 in the normal way (backing up and restoring /etc/samba and /var/cache/samba). However, the real issue is that

We have Samba 3.2.4 on two SLES 10 (one is SP1, the other SP2 64bit) machines. Both are member servers in our ADS, which was over the past month given some additional DCs, new IPs for all DCs, and upgraded to Windows 2008 (from win2003). The krb5.conf and nsswitch.conf files on the two machines are identical; the smb.conf files are *nearly* identical in their common section; the filewall rules

Hi. Does winbind has limitations with lots of users in domain? I'm compiled samba 4.3.1 and created 40 users, so winbind and getent works fine, but when created 26.000 users and "wbinfo -u" doesn't show users. On DC Member Server, "wbinfo -u" and "getent passwd" doesn't show users to. On log.wb-CORP appears: [2016/02/23 18:46:46.319393, 1]

Hi folks ! Has someone any idea on this issue on AIX 5.3 TL 10 with winbind ? I'm really stuck now ... I think everything is working pretty well with WINBIND and AD 2k3 , but not my most important point : I absolutely need the Secondary groups of each AD user which get connected to the AIX to use this filter with sudo... I only get Primary Group (which is by default "Domain Users"

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:

Hi, on a customer system samba/winbindd is used for windows and unix authentication. I just tuned searches of the ldap backend to speedup by factor 20-200 and slapd now doesn't seem to be the bottleneck anymore. Don't know how well the windows authentication now works, since this is presently done by the heartbeat failover server. However, simply starting 'mc' as root makes

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

Hello, I have set up winbind to authenticate linux pc's to a windows 2003 AD. The authentication works, but the performance is not good (takes over 5 minutes) PRELIMINARY ----------- OS: ubuntu 7.04 Samba: 3.0.24 AD: windows 2003 ANALYSIS --------- After analyzing the log.winbindd file in log level 10, I can see three major parts 1) lookup and authenticate the user -> performance OK

Hi, We recently upgraded some AD member file servers from 4.6.7 to 4.6.11. Since then, "getent group" has been failing to return groups properly after winbind's been running for a couple of days. We have a lot of entries in log.wb-<DOMAIN> like this: [2017/12/15 11:39:47.959368,  1] ../source3/winbindd/winbindd_ads.c:1236(lookup_groupmem)   lsa_lookupsids call failed

Hi guys! I started to have the problem above last October, 2th. I don´t know why and how, because it was saturday. So, my file server stoped to authenticate against the Samba4 AD. Today, all shares was stopped and then i restarted my Samba4 AD and the file server. All became to work again. But it im afraid because the problem started by itself. Thanks! # MY CRONTAB 17 * * * * root cd /

Dear samba list, For some time we've had servers connecting to a w2k3 r2 server via ADS setup. Wins was working fine and users were able to authenticate. Recently we've added a GFS like system. This required getting the UID/GID's unified. Suggestions were made on the samba IRC channel to install SFU on the PDC. I'm receiving some very strange output. Usernames/pwd have

Greetings, Upon a suggestion to improve the --timelimit patch, I have also added a --stopat option. You can get the patch from this URL and/or cut/paste it from below. http://www.terry.uga.edu/~jft/rsync-timelimit-stopat.patch.gz Here are the details... --timelimit=T This option allows you to specify the maximum number of minutes rsync will run for. This time starts when

I am running Samba ver 3.0.37 on Solaris 10 (sparc) as a PDC with LDAP for the backend for both samba and unix accounts. Assume the samba SMBPDC is called "PDC." I have also set up a trust with an Windows domain- lets call it WINDOMAIN- (the PDC for the Windows domain is Win 2003 but is in mixed mode for backwards compat.) The SAMBA domain trusts the WINDOWS domain, not not vice