similar to: LDAP: PDC to BDC replication issues

Displaying 20 results from an estimated 100 matches similar to: "LDAP: PDC to BDC replication issues"

2018 Mar 05
0
Fwd: Migrating server
Am Montag, 5. März 2018, 22:16:36 CET schrieb Rob Thoman: > Hi Gruss, > > At this stage there is only one server, running 3.6.25 on Ubuntu12.04. > The plan to get LDAP to work on this one. Then add the second server > 4.x and the promote it to BDC and then demote this one. Just a side > info, we didn't want to go tdbsam in both as I read it breaks the > domain trust.
2018 Mar 06
3
Fwd: Migrating server
Hi Gruss, Had to ditch the VM and start again. Here is the info: tdbdump secrets.tdb |egrep -v '^data|^}|^{' key(21) = "SECRETS/SID/mydomain" key(18) = "SECRETS/SID/sam3dc" key(42) = "SECRETS/LDAP_BIND_PW/cn=admin,dc=mydomain" key(25) = "SECRETS/DOMGUID/mydomain" key(42) = "SECRETS/MACHINE_SEC_CHANNEL_TYPE/mydomain" key(42) =
2018 Mar 08
1
Fwd: Migrating server
Hi Harry, Here are the outputs. I've attached them as logs with this email too. root at sam3dc:/tmp/ldifs-gr# ldapmodify -Y external -H ldapi:/// -f olcdbindex.ldif SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={1}hdb,cn=config" root at sam3dc:/tmp/ldifs-gr# service slapd stop
2018 Mar 08
3
LDAP BDC- Classic Domain
Hi Guys, We're trying to add a BDC in Samb4 classic domain setup. The Samba 3 How -To and Samb3 by Example covers this but uses the old slapd.conf option, we are using the slapd.d config. I couldn't find a similar document for Samba4 Can you please advise that the following steps will work? LDAP in the existing PDC is working using the smbldap tools - Setup the LDAP in BDC
2018 Mar 08
3
Fwd: Migrating server
Hi Harry, sadmin and tadmin are both admin logins. I was trying to domain join with both. sadmin is in ldap The olcdbindex.ldif gave this error SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={1}hdb,cn=config" ldap_modify: Other (e.g., implementation specific) error (80) additional
2013 Aug 05
1
TLS between winbind and openldap
Hi, I'm working hard to setup winbind and openLDAP work together with TLS My networks contains: - a windows server 2008 R2 domain controller - a debian 6 based file server (openmediavault v0.4) running OpenLDAP 2.4.23 and Samba v3.5.6 - a debian 7 computer running winbind 3.6.6 I want to let OpenLDAP store SID <=> uig/gid mapping to ensure constant uid and gid for users on all linux
2018 Mar 05
9
Fwd: Migrating server
Hi Gruss, At this stage there is only one server, running 3.6.25 on Ubuntu12.04. The plan to get LDAP to work on this one. Then add the second server 4.x and the promote it to BDC and then demote this one. Just a side info, we didn't want to go tdbsam in both as I read it breaks the domain trust. The domain names are real ones. I ran the commands you suggested, nothing in reply. I tried
2018 Mar 02
0
Fwd: Migrating server
Hi Rob, please stay on list. Otherwise I will charge you :-) By the way I have no problem to get payed. > Hi Harry, > > The one very obvious difference is the result of this command: # > ldapsearch -xLLL -b dc=afrika,dc=xx -s sub -D > cn=admin,dc=afrika,dc=xx -w 'sambadomainname=*' > dn: sambaDomainName=SCHULE,dc=afrika,dc=xx > > I get dn:
2010 Jun 11
1
dns.keytab
Hi guys I setup my samba4 server with provision. (pdc1) Then I setup a DC using net vampire after rolling back to commit 62e0a74 to bypass mdw updates that broke net vampire. (pdc2) I had to manually add to the zone in pdc1 the follwoing records to get replication to work: I made all the modifications in named.txt to bind pdc2 IN A 192.168.48.236 <PDC2-GUID>._msdsc IN CNAME pdc2
2010 Jun 09
2
DC replication
So finally I got the net vampire to work. I had to roll back to commit 62e0a74 bypassing all the updates done by mdw at samba.org for now. Now the replication PDC1 is the first domain controller created by provision PDC2 is the second is the second domain controller created by net vampire on PDC1 I added user using "net newuser testuser1" in few seconds it appeared on PDC2 using the
2006 Feb 21
0
nobody run "add user script = /usr/sbin/useradd ....."
Greetings! I have the following configuration: Two PDCs with Fedora Core 4: PDC1 and PDC2. PDC1 trusts PDC2, respectively PDC2 is trusted to PDC1. I join an XP workstation to PDC2. After restart i can see both domains in the login screen domain combo box. I can logon to PDC2 , but not to PDC1, since the PDC2's /etc/passwd
2006 Feb 27
0
Two PDCs Samba trustrealtionship --> winbind configuration
Greetings! I have the following configuration: Two PDCs (Samba 3.0.21b) with Fedora Core 4: PDC1 and PDC2. PDC1 trusts PDC2, respectively PDC2 is trusted to PDC1. I join an XP workstation to PDC2. After restart i can see both domains in the login screen domain combo box. I can logon to PDC2 , but not to PDC1, since the
2004 Feb 18
1
password server
Hi ! If someone could help me.. I'm trying to ask my server to validate password on a first pdc in domainA and on a second PDC in domainB. However, when I set password server in smb.conf like this : password server= PDC1, PDC2 It only validating from PDC1.. I think that samba suppose that PDC2 is a bdc of PDC1. Any suggestion ? Excuse my poor english, it's not my native language.
2005 May 15
0
Inter Domain Trusts
Hi, We've tried to set two servers PDC Samba 3 + OpenLDAP as following below: Network_1 192.168.42.0/24 Network_2 192.168.43.0/24 PDC1(PRJLINUX1) - 192.168.42.2 - NETBIOS NAME = PRJARQ6 PDC2(PRJLINUX2) - 192.168.43.251 - NETBIOS NAME = PRJARQ5 OpenLDAP 2.2.24 Samba 3.0.14a Backports Deban 3 Woody OpenLDAP: The servers are using the same DataBase and the PRJARQ6 is a Slave from PRJARQ5.
2010 Jun 05
1
wins or windbind problem? - help please
I have four domains in my LAN. I set up trust relationships for the domains, having each PDC working as wins server for each domain but I hd not set up winbind. I have samba3-3.3.12 + ldap (openldap 2.4.21) as users backend. I mean, I have wins support = yes for each PDC, and I can access to the shared folders of each PDC from any windows computer from my LAN. The problem is accessing to
2013 Jan 28
0
trouble with ldap authentication on centos+openldap
Hi Samba List, I've been trying to get a samba+ldap working on centos 6.3. I've had some troubles adapting to the new slapd.d configuration format for the openldap, which seems unnecassarily complicated. Most of the tutorials refer to the older style slapd.conf configuration. I was following this tutorial:
2018 Mar 02
1
Fwd: Migrating server
hai, im still on holiday but i did see some things a bit, also in addition about the smb.conf in classic mode dns forwarder is predecated, so i suggest avoiding the option. this part, you set ssl off but also set the ports to the ssl ports. ldap ssl = off ldap passwd sync = yes /etc/ldap/ldap.conf BASE dc=mydomain URI ldap://sam3dc.mydomain ldap://sam3dc.mydomain:666 use URI
2018 Apr 26
0
Password change
On Thu, 26 Apr 2018 13:57:12 +1000 Robin G via samba <samba at lists.samba.org> wrote: > Hi Rowland, > > I tried that but didn't work. > # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. > # CRC32 9033b998 > dn: olcDatabase={1}hdb > objectClass: olcDatabaseConfig > objectClass: olcHdbConfig > olcDatabase: {1}hdb > olcDbDirectory: /var/lib/ldap >
2004 Oct 01
1
Locking/Timeout Problems
hi, we using samba3.0.7 with a ldap(tls). it works fine. no problems with dns (reverse) lookups etc. all 20 xp clients can logon fast into the samba machine and access all shares. the problem since 3 weeks is, that after a while all shares freeze for 10-20 seconds in a user session and the user have to wait to continue. not all user at the time. the user get no response from explorer, the
2002 Oct 28
2
auth to two diff PDCs? (success, sort of)
With a single server, settings "security = server" and "password server = pdc1 pdc2', I can successfully authenticate against two entirely different PDCs depending on which order I put the two machines in the 'password server' list. Is there someway of forcing clients from either domain to authenticate against the 'right' pdc, regardless of the order in the