similar to: configuring a backup domain server

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 olcSuffix: dc=testdom olcAccess: {0}to attrs=sambaNTPassword,sambaPwdLastSet,sambaPwdMustChange by dn="cn=admin,dc=testdom" write by self

Hello, I have a question about machine accounts. I using Samba 3.0, OpenLDAP 2.1.30 and Berkeley 4.2.52 on backend on RedHat machines. I also have 3 slave/BDC's and 1 master/PDC Right now all of my users and groups exist entirely in the LDAP directory. I have a few accounts in addition to the normal system accounts that are used for emergency access. All authention and group enumeration uses

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

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 , I use Samba 3.4.7 PDC + ldap backend . I can't put the machine if I don't specify the wins server on Pc-client. I try different name resolve order , but nothing change ? Can you help me ? My global is : [global] workgroup = workgroup netbios name = SERVER server string = Server Samba wins support = yes browse list = Yes remote announce = 10.0.0.255/workgroup

Hi , I use Samba 3.5 PDC + ldap backend . I can't put the machine if I don't specify the wins server on Pc-client. I try different name resolve order , but nothing change ? Can you help me ? My global is : [global] workgroup = workgroup netbios name = SERVER server string = Server Samba wins support = yes browse list = Yes remote announce = 10.0.0.255/workgroup

Hi list, My brand new samba network is working pretty good, ironing out some glitches. Win XP users cannot change their password. I use SaMBa as a domain-controller with an LDAP backend. A stripped down version of the config is below. I set minimum password length to 8, trying to change the password to a 7 char long gives me the messages that the password does not meet requirements. So that

Hi All, I'm having a problem with cross subnet browsing and name resolution across an openvpn tunnel. i've found quite a few people who've had the same on mail lists but none of their fixes have worked. The spec of the setups at both ends of the tunnel are as follows: OS - CentOS 5.5 Samba Version 3.5.4 OpenVPN Version 2.0.9-1 Each server is configured in gateway mode with two NICS,

I've almost got it. I swear I've almost got it (and I've been doing a lot of swearing lately). I re-built my PDC, starting from scratch. I'm not using the editposix extensions anymore - I'm using the smbldap tools as shown (I think) in the Samba by Example. I really really thought I did everything right. Obviously I was wrong. What works - all my workstations and

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 All, I'm having a problem with cross subnet browsing and name resolution across an openvpn tunnel. i've found quite a few people who've had the same on mail lists but none of their fixes have worked. The spec of the setups at both ends of the tunnel are as follows: OS - CentOS 5.5 Samba Version 3.5.4 OpenVPN Version 2.0.9-1 Each server is configured in gateway mode with two NICS,

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

What about your openvpn config? The tun net must have an entry in your hosts allow. If you work with briding the remote network has to be the same subnet as the local!? Bridging is the best way to have a remote net integrated. I have one logging in form Berlin on my Samba-Domain. Daniel ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik

Hi community. Let me tell you what happed to me. I configure samba to authenticate to an LDAP server, everything wokrs perfect, I got rid of the /etc/passwd file, now all my users reside in the LDAP database, I can connect via ssh for example without any problem, getent passwd returns the information as expected, till here just like a sharm. No, I connect from a windows 2000 client as

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

Running samba-3.0.24 with ldap on debian etch. Whenever I try to add an xp pro machine to the domain I get (on the pc) "the username can not be found". I'm loggin in as admin. In the samba log I get (for this pc) " passdb/pdb_interface.c:pdb_default_create_user(368) _samr_create_user: Running the command `/usr/local/smbldap-tools/smbldap-useradd -w

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

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, I have a little problem with my Samba PDC setup. I have a Debian / Etch with Samba 3.0.24 with OpenLDAP Backend and use it as PDC with domain logons and roaming profiles enabled. The logon for normal domain users work without any problems, but when I login with my domain administrator account my Windows XP Professional client I have a big problem. After the logout, when it tries to copy

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