similar to: syncrepl in OpenLDAP 2.3.x (CentOS 5) and updating on a replica

Hello everybody,, This time i want to replicate PDC to BDC when there's is any changes on PDC, here is my conf. on /etc/openldap/slapd.conf LDAP Server master moduleload syncprov overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100 LDAP Server mirror moduleload syncprov syncrepl rid=001 provider=ldap://ldap.domain.com:389 bindmethod=simple

Hello all, I have setup an HA cluster running under Debian GNU/Linux with samba 3.0.7, openldap 2.0.23 with two machines. Each machine runs winbindd and slapd. One additionally runs slurpd to replicate to the other. Replication works but winbind seems to add entries on the secondary ldap server and not follow the updateref given from the server. This is a problem since the ldap database run

Hi to all! I've set up Zimbra LDAP (2.4) as master, and I want to use RHEL v5 LDAP (2.3) as a slave. This is relevant part of my slapd.conf on LDAP 2.3: # syncrepl directives syncrepl rid=101 provider=ldap://192.168.1.86 bindmethod=simple binddn="uid=zimbra,cn=admins,cn=zimbra" credentials=PASSword searchbase="dc=company,dc=com" schemachecking=on

Hello, I have two ldapservers with Samba PDC and BDC. I started with the PDC i use Suse 9.0 with ldap "out of the box" and Samba 3.0.2a. Everything is working fine with only the PDC running. Now i configured replication. In my slapd.conf file on the master server i added the following lines #permission access to * by dn="cn=repl,dc=felix,dc=local" write # database definition

I've setup an LDAP server with a slave server on Centos 5.3 X86_64, replication works, most of the time client logins work fine but I'm starting to get a error I can't seem to eliminate, it's starting to cause login failures for users and I think it's causing other application failures when they try to auth against ldap. on the client side /var/log/messages shows Oct

Hi, I am using both syncrepl (for replication) and smbk5pwd (for password synchronisation between samba and ldap account) overlays. I have configured replication in the simplest way: a read-only producer that forwards updates to the provider thought updateref. If I change my password thought passwd command on a client with pam modules configured for gaining information from the provider

Hi, I'm having problems deleting something from 389DS. At one point I had a link to use an external LDAP server for authentication for a particular client. I now need to delete this but I am having trouble. Firstly I can't find this object in either the directory manager or ldapadmin. I can see the object using db2ldif: # entry-id: 1838 dn: cn=bloggsco,dc=mycompany,dc=com

Hi, I configured a SaMBa PDC and a BDC with a master and a slave OpenLDAP. I set up TLS, because I wanted secure syncrepl. Slapd runs with -h ldap:// 127.0.0.1/ ldaps.///. I successfully joined an XP client to the servers' domain, I see shares (but I havent logged in as a domain user, because I have to create a default profile first). My problem is in the log.winbindd-idmap log file:

I'm (finally) getting around to putting a backup LDAP authentication server on my network. The backup uses syncrepl to grab the database, and to my eyes both LDAP servers answer read queries identically. I'm testing the client side of this configuration on virtual CentOS 5 i386 machine. /etc/ldap.conf reads ----- %< ----- base dc=DOMAIN,dc=com timelimit 30 bind_timelimit 30

Hello Samba Users, Simo and I have put together a new document which includes the latest replication methods using Openldap. Instead of using the ageing slurpd for replication (which is no longer actively developed or supported); Openldap as of version 2.3 supports a new feature called delta-syncrepl. http://wiki.samba.org/index.php/Replicated_Failover_Domain_Controller_and_fi

I'm trying to setup OpenLDAP on CentOS7, in a provider/consumer relationship. In general, provider/consumer is working quite well, except when it comes to password policy. Specifically, I want PwdFailureTime to be written to the provider from one of the front end consumers when appropriate. I'm lead to believe this requires: a) ppolicy_foward_updates TRUE (done) b) an appropriate

AIX 5.2 OpenLDAP 2.2.15 Samba 3.0.7 (no winbindd) I've got a stupid problem with referrals that I can't seem to ferret out. Each Samba DC has a localhost-based LDAP replica for scalability (my idea anyway). So the only way they will talk to the Master is if there is need for an update. Ok. If I make the updatedn the same as the rootdn of the replica, it updates the local database;

All, After many hours of research I have found there is a incompatibility between OpenLDAP V2.3.x and V2.2.x, or atleast between V2.3.27 the current version on CentOS V5 and V2.2.13 the current version on CentOS V4. The syncrepl feature of OpenLDAP, to keep multiple slapd servers sync'd, was working between CentOS 4 and 5 at one time, as that is how I populated the "slave" servers.

On Wed, 25 Jan 2017 15:55:16 +0100 basti via samba <samba at lists.samba.org> wrote: > Hello, > > at the Moment we use and Samba 4 in NT4-style Domain with approx. 20 > Clients. > > With the Problem of Windows 10 to join to NT4-style >

Hi, From what I gather, OpenLDAP on Centos 5.x pulls LDAP changes from central LDAP server to a secondary LDAP server. So in other words, you can have your second LDAP server pull the db based on either; type=refreshOnly which mean the pull interval will happen when ever you specify or; type=refreshAndPersist which mean after a pull, keep the pipe open for any changes made. Now in

Is this Samba 3 or Samba 4? If samba 3, which ldap server are you using> What is the mail server? Does the mail server have its own LDAP server included it or is also using an external LDAP server. If you want replication between LDAP servers, they should be the same type of LDAP server (e.g. OpenLDAP or Apache Directory Server or Oracle Directory Server.) If you have one

Hello, at the Moment we use and Samba 4 in NT4-style Domain with approx. 20 Clients. With the Problem of Windows 10 to join to NT4-style (https://wiki.samba.org/index.php/Required_Settings_for_Samba_NT4_Domains#Windows_10:_There_Are_Currently_No_Logon_Servers_Available_to_Service_the_Logon_Request) we plan to migrate to Samba AD. At the Moment there is the following scheme: samba PDC

I have two instances of an openldap-2.4.39 server running with syncrepl in a master-master replication setup. These are Centos 7.1 test servers which have been running for over 2 months now with no problems. Partly the good behavior of the LDAP servers is due to very little exercise. Yesterday I decided to try and see exactly how well replication was working. With server-2 up and running I

I'm trying to get Samba up but I can't seem to get the LDAP connection working correctly. I can run a search from ldapsearch, but samba is complaining that it can't connect. Here's the error from log.smbd [2004/12/29 16:04:04, 0] lib/smbldap.c:smbldap_connect_system(850) failed to bind to server with dn= cn=Manager Error: Invalid credentials [2004/12/29 16:04:04, 1]

Hi I am trying to upgrde ?out openldap ver 2.3 ?to the lastest version 2.4, howevre there is no rpm avaibale for 2.4 so i decide to create my own for centOS flavour 5.2 here is the ?part look of my spec file openldap.spec Summary: openldap Installer Name: openldap Version: 2.4 Release: 1 Vendor: net Solutions License: Commercial Group: ms6 BuildRoot: /usr/src/redhat/BUILD/openldap Provides: