similar to: Unable to change Windows password on Samba BDC

Dear Help, Here is my situation: We have offices located in several areas around the country, all of which can communicate with each other through VPNs we have established. I have set up a Samba domain in which the PDC is located here in our home office, and there are BDCs for the same domain in each of the remote offices. I have been able to successfully join machines here in our home office

Hello I makeing a Domain Controller with Samba (v3.0.33) and LDAP (v2.4). I will install a PDC in the headquarter and a BDC in the subsidiary of the company that I work. The PDC and the BDC will have his own LDAP data base. I just install the PDC without problems and my next step is to install the BDC. I configured the LDAP that work in multi master mode. I made some test and the LDAP works

Greetings, I have a Suse 9.3 server running 3.0.9 as a PDC, using OpenLDAP as the passdb and idmap backend. I also have a 3.0.9 server set up as an OpenLDAP slave, but it only serves files. I decided that I'd like to set this other server up to service logins as well. When I add the "domain logons = yes" in this server's smb.conf file, I get some rather strange behavior.

I have noticed while testing my Samba 3.0.2a primary and backup domain controllers with Windows XP clients, that when I attempt to login to the Samba PDC, the XP client will sometimes randomly choose the backup domain controller. I only want the client to join the backup domain controller when the PDC is offline. I am not experiencing any random network outages or DNS failures so I am bewildered

I have a PDC+LDAP as well as a BDC+LDAP in another subnet setup with a domain member in the same subnet as the BDC. From my understanding the domain member should be hitting the BDC for all authentication but watching the logs I see the PDC is the one handling it all. The BDC just sits there. Am I missing something? Here are the smb.conf for each servers: PDC: [global] workgroup = X.X.X

Hi, My doubt is about Idmap + LDAP + winbind, related do BDC + PDC. We are using Samba 3.0.33 (Slackware 12.0.0). Our layout is almost like this one http://us1.samba.org/samba/docs/man/Samba-Guide/images/chap6-net.png, but we have more BLDGn than this example. Actually, we are taking ideas from http://us1.samba.org/samba/docs/man/Samba-Guide/happy.html and from

We're about to start migrating from Windows NT 4.0 to a Samba controlled setup. I've got a question about the functionality of the Samba PDCs and BDCs. In my Windows setup I have three domains that are defined by geographic locations. Each of these domains "trusts" the other. In Samba 2.2.7, I can't have the trusts, so I'm looking at creating one giant domain that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to get a samba setup with with a pdc/bdc configuration. The backend information stores are openldap ( for passdb and idmap ) I have followed the instructions in the Samba Guide and the documentation provided with the smbldap-tools package. Samba version: 3.0.24 smbldap-tools: Using the version included in samba (

I have a Samba PDC (Ubuntu 12, OpenLDAP 2.4.28, Samba 3.6.3), and at two remote sites, I have some Samba BDCs. For now I've manually entered the DCs as WINS servers on the workstations I'm using for testing. At the remote sites, I can log in with an account that has no logon path or logon home specified, and it works perfectly. But at the main site, when I try to log on to one of these

Hello, Just wondering what I should be using for the password change program on a BDC. Should it be: passwd program = /usr/bin/smbpasswd -r <PDC address> %u I'm having a problem with passwords not staying in sync between the PDC and BDC with pass backend ldap. The systems are all Fedora Core 4, Samba 3.0.14a, openldap 2.2.23 Kent N

Hi every body, As you may have guessed, I've got a problem ;) What I had : - A PDC Server (Windows NT 4 SP 6a), called SERVER1, for the domain TEST - A BDC Server (Windows NT 4 SP 6a), called SERVER2, for the domain TEST Everything was working fine. Now I switched my NT PDC to a Samba PDC, and I make SERVER1 a BDC for the domain. Until now, no problem. I use samba 3.0.4,

Have you set in the slapd.conf on the slaves something like updateref ldap://master.ldap The slave / consumers need to redirect the request to the master ldap database. It may also be a good idea to have samba use fail over for the ldap backend. You would need to set this in your ldap.conf as too. for pdc / ldap master passdb backend =ldapsam:"ldap://master.ldap ldap://slave.ldap"

When I stop the BDC all clients log on to the PDC. And to my confusion when I restarted the BDC today and made a testparm on both PDC and BDC both showd role domain pdc --> Server role: ROLE_DOMAIN_PDC Here my smb.confs: PDC: [global] security=user smb ports = 139 logon script = logon.bat logon path = \\%L\%U\profile\%U logon drive = S: domain

Hi Im looking to config a BDC with ldap. It seems the connection with ldap primary server works, but Im confused with the shared folders. I understood when you creates a BDC needs to put the same global information: [global] workgroup = DOMAIN netbios name = DOMAIN-PDC security = user enable privileges = yes interfaces = 127.0.0.0/8 eth0 10.0.1.0/24 10.0.0.0/24 server string =

Hello, I am trying to figure out how to implement a samba domain in a number of remote offices around the world with partly bad and often interrupted WAN connections/VPNs. The goal is to administer the directory from the central data center. My obvious choice would be to set up a central server with SAMBA+OpenLDAP+smbldap-tools and in each remote office a SAMBA server with OpenLDAP as a

Hi, We have an old domain with a samba-3 PDC and LDAP backend in our HQ and two BDC in our branch offices. Since we don't use the domain in our HQ anymore and one of the branches will be moved to our new domain (2003/2008) I'm thinking about decomissioning the PDC and promote both BDCs as PDC for their branch offices and networks. I would also get rid of LDAP. Changing the backend to

Hi samba folks, I'm running an NT$-style samba PDC and 2 BDCs. They are all on samba 3.6.25 (the SERNET packages on debian wheezy) I have a domain trust with another server on another subnet, I think they run samba 3.5, also NT4-style domain. Everything ran fine, they can login to our machines and vice versa, winbind can resolve their usernames etc. Now I upgraded the PDC to debian jessie,

hi, until now (about 1 year ago) i was working only with samba3+ldap PDC, but in near future my company enlarge his network with 6 new branchs spreaded all oever the country and i must build a scalable network with Samba-3 PDCs and BDCs, implement LDAP replication and multiple LDAP backends, all this over some VPNs(ipsec) . so, can tell me anyone how work the relationship beetwen a samba3-ldap

My Configuration, On my PDC: Samba version 3.2.15 /LDAP-Master (slurpd)/SMBD4wins <-- version 3.3.12 not working. Downgrade again On my BDC: Samba version 3.3.12 /LDAP-Slave <-- version 3.3.12 working [global] on PDC [global] workgroup = tuepdc.local bind interfaces only = true interfaces = 192.168.135.143/24 127.0.0.0/8 socket address = 192.168.135.255 profile acls = no hosts allow

I recently set up a backup domain controller using Samba 3.0.23. I have a Samba PDC already running, and all is working fine, but once I added the BDC, now when people log in to their windows account, their home directory is now being mapped to their home on the BDC (which is empty) instead of the PDC. Conf files from each below: PDC Samba Conf: [global] unix charset = LOCALE