similar to: Samba 3.0 a BDC to a Samba 2.2.7 PDC ?

Here's my situation: I currently have Samba (v. 2.2.7) running on RedHat 7.3, configured as a Domain Controller. Users are logging into the domain and everything is working fine. I must 'upgrade' to RedHat Enterprise Linux ES 3.0. I say 'upgrade', but what I actually have to do is a complete OS install, NOT an upgrade (there is no upgrade path to RHEL3.0 from anything

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

Hey all, might be a tad bit off topic to samba, but not entirely unlrelated. Anyhow, as I understand it, the task of a BDC is to process most if not all of the domain logons before a PDC does so is it not? It has been my understanding that the BDC generally accepts and processes domain logons before the PDC does on a network to keep the load down on the PDC until such time as the BDC cannot

I have a server acting as a PDC, and another server acting as a BDC. When I run 'net getlocalsid' on each, they return different numbers. If I run 'net getlocalsid domain_name' on the BDC, it returns the PDC's sid. Is it import for each machine to have the same SID? Thanks, Chris

Hi the list, I am in a process of converting a Samba PDC to BDC and a BDC to PDC am running into some issues. 1. For each of the samba servers, I have two configuration files. One is for PDC and the other for BDC. I make a symbolic link from one of the two files to /etc/samba/smb.conf. Then I do "service smb reload". The problem I have is that Windows clients do not see the

We are using Samba as a Domain Controller. Some of our Windows servers think that they are the domain controller. This is sending event 5719 and event 8032 errors on several of our windows servers. Any suggestions on how to keep our samba DC in control of these issues? Thanks. os level = 255 wins support = yes local master = yes

All, I'm using an LDAP backend for a test PDC/BDC setup. Both the PDC and BDC are using the same LDAP server. Both the PDC and BDC are running 3.0.23c on Sarge, and I've verified that both the PDC and BDC will authenticate users via smbclient. XP clients are able to login to the domain fine, and all is generally swell. My PDC is also my WINS server, and I've verified that XP clients

On Wed, 28 Sep 2016 16:11:23 +0000 Charish Patel via samba <samba at lists.samba.org> wrote: > Hi folks, > > I've been tasked with a migration of our servers and, as the subject > implies, part of it involves a PDC and BDC that were set up before my > time. However, I'm trying to accomplish a little bit more to give > myself, the sysadmin, a little bit more

On Wed, 28 Sep 2016 11:33:29 -0500 Bob of Donelson Trophy <bob at donelsontrophy.net> wrote: > On 2016-09-28 11:22, Rowland Penny via samba wrote: > > > On Wed, 28 Sep 2016 16:11:23 +0000 > > Charish Patel via samba <samba at lists.samba.org> wrote: > > > >> Hi folks, > >> > >> I've been tasked with a migration of our servers

If you mean regular Microsoft AD, the reason is simple: cost. Management sadly does not want to shell out the money for it. If you mean upgrading the Samba PDC to AD, that is what I want to do but on the new servers as opposed to the current set up. Charish -----Original Message----- From: Rowland Penny [mailto:rpenny at samba.org] Sent: Wednesday, September 28, 2016 12:23 PM To: samba at

Hi all! I want to implement a samba architecture with one PDC one BDC and 1 file server acting as a domain member server in a lan with approximately 60 clients. Even if they are not so many I need a solution that can give scalability to 100 clients in near future and reliability in case of hardware fail. Therefore I'm going to configure this system in order to obtain redundancy in user

Hey list, I've got a problem with my PDC/BDC setup. They're both running 3.0.23c on Sarge, and I've verified that both the PDC and BDC will authenticate users. test-pdc:/etc/samba# testparm Load smb config files from /etc/samba/smb.conf Processing section "[netlogon]" Loaded services file OK. Server role: ROLE_DOMAIN_PDC test-bdc:/var/log/samba# testparm Load smb config

Software: OS: Redhat 9 Samba Ver: Samba 3.0.0 (Plus excel writelock patch, waiting for 3.0.2!) OpenLDAP Ver: 2.0.27-8 Just a quick question about PDC / BDC interaction, my plan is to distribute Samba (with slave ldap backend) BDCs to remote facilities, as well as have one on each network segment in the hopes of avoiding unnecessary nmb broadcast traffic. My question is this: Will the PDC /

Hello, I have a little problem with samaba... well... with windows nt, samba works fine. I'll try to explain it: My net has 2 servers with NT4, a pdc and a bdc. Well, my intentions is to eliminate de NT4 PDC and put a Samba PDC. So I made the next steps: 1-. In BDC, Administrative Tools - Server Administrators (i think) and there i select the BDC and click in the menu to "Eliminate

Hi, Maybe this was asked many time (although can't find it on google). Let's assume 2 scenarios: 1) I've got local network where PDC and BDC are set up. PDC is working fine so the BDC is. When it's possible for any XP client to use BDC instead of PDC? I read in samba docs that if PDC is slow client can use BDC - but what does it mean slow for the client? How the client knows

Hi all! I'm a bit unsure if my idea is the best approach to this. So here's what I'm supposed to do: There is currently a samba pdc running with samba-2 which is about to be replaced because of some strange behaviour. The idea is to build a bdc first which should take over the job of the pdc as long as it takes to set up a new pdc with samba-3. After that is done the pdc is brought

Hi there, I have a Samba PDC and BDC migrated from NT4 using ldapsam with an interdomain trust to a 2k3 domain. The trust is established both ways and was made from the pdc. Using samba 3.0.14a-sernet on Suse 9.1 The trust is working. I can pull users from the trusted domain and apply them to acls on my samba DMS. Winbind adds the idmap entry correctly. What is not working, is authentication from

Hello all, I have 2 PC setup as PDC and BDC (both Centos5, with samba 3.0.23c-2). The problem is, quite often client logon to BDC instead of PDC. I tried to tweak the OS level, but seems not affecting the problem. My understanding is that BDC will only taking charge of client logons when PDC is unavailable. Or is it that BDC will work hand-in-hand at the same time with PDC regarding domain

Hi, Does someone know how will all my client machines find the BDC when the PDC is stopped. Both PDC and BDC are running Samba with LDAPSAM backend replicated on both the PDC with master LDAP database and BDC with replicated LDAP database. But when I stop PDC the clients are not detecting the BDC broadcast. The replication on all domain controllers are perfect. I went as far as making BDC

I would like to know how to achieve a "hot-failover" setup between a Samba 3.x.x primary domain controller and backup domain controller with a LDAP backend. I was under the impression that all I need to specify is something like the following in my smb.conf: passdb backend = ldapsam:"ldap://pdc-srv.domain.org ldap://bdc-srv.domain.org" I have set this passdb backend