search for: ldap_next_entri

Hi, I use samba 3.0.26a on fedora 8 as a fileserver for a win 2k3 domain. This has worked fine for about 2 months without any problems. However I came to the server 3 days ago and the harddrive was 100% full. On checking I found 60gb of core dumps in the winbind folder. I did a lot of searching and couldnt find anything relevent for this release. I tried upgrading samba to 3.0.28 (fc8

Greetings We've moved from using NIS/SFU to using Samba/Winbind connecting to our Windows 2003 AD domain with an Openldap idmap backend on our Redhat 4/5 servers. We managed to get this mostly working in that users can authenticate using their domain accounts (thank you Samba team!!!). We do however keep getting the same error in the log.winbindd-idmap log: winbindd:

I have recently upgraded a Samba server running on a Red Hat Enterprise 4 (32 bit) server. The version of samba upgraded to is 3.0.25b. I noticed that a new index had to be added to my ldap (openldap) server for the sambaSID attribute. So I added the index line to slapd.conf as follows: Index sambaSID eq,sub Afterwards I ran slapindex to recreate the indices in the openldap database.

Hi, I have written a php script to upgrade a fresh s4 AD with more details from a (s3) ldap server. I am no programmer AT ALL, so I guess this is very dirty and un-elegant, but it does the trick. We had multiple "mail" attributes in openldap, and since AD only allows 1 mail attribute, additional mail addresses are migrated to "otherMailbox" AD attributes. Perhaps someone

Hi, We are trying to implement a highly secure mail server with user authentication restricted to SSL certificates only (not using passwords at all). Still, user information is stored in a LDAP directory. In this configuration LDAP is used to check whether the user is registered (and probably supply quota and other info), and actual authentication is done by SSL layer. According to wiki, a

I managed to do migration using "classicupgrade". Doing tests with debian buster 2:4.9.4+dfsg-4. For the moment using samba internal dns and sub-domain of ad.advocap.org. Had issue forwarding dns if I used main domain. When it comes to real production will use bind that I understand better but don't want to mess with my other dns servers now. Had a w10 box join samba4 ad