similar to: Replacing WinNT 4 PDC with Samba PDC

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

I've got a Samba 2.2.7a domain with an LDAP backend. It's been working for nearly 3 months now without much bother. By the way: Great work and thanks for all of the effort! I have been missing one minor thing from the setup since I moved away from NT 4: Password Expiration. In the past I have posted questions about this on the list and I've gotten two answers: "Wait for

I've had a Samba 3.0.2 Print Server running for nearly 7 months now without too much of a hitch on RedHat Enterprise "ES" 3.0. Late last week, RedHat issued an Errata that moved Samba from the 3.0.2 base to the 3.0.4 base. So when I did the "up2date" this weekend as part of my normal maintenance, this server was updated and everything appeared to be fine. Things are

I have an NT4 PDC that I would like to replace with a Samba server. My network also has a box running MS Exchange and Backoffice (not the same box as the PDC). What's the general roadmap for doing this? Could I install Samba as a BDC and then promote it. Should I create a new domain on Samba and do a big cutover? Or is there a way to just get the necessary info off the PDC and then

Since we're on the subject of Samba over the WAN.... (BTW, I'm running three offices with a Samba 3.0.9 PDC and two Samba 3.0.9 BDCs over an FreeSwan based WAN and it works just fine. The WINS server is a must in my book though.) Last Thursday and Friday, one of the remove office's WAN lines went down. While the outages were significant, nothing major happened because of it. But,

> -----Original Message----- > From: samba-bounces+kcollins=nesbittengineering.com@lists.samba.org ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Looks like it's the Virus is forging my address now... :-( Jeesh. What a waste. If the guys writing viruses would put their energies into REAL code, we'd be so much farther ahead. Later, -- Kevin L. Collins, MCSE Systems Manager

Hi All: Stuff I'm using: Red Hat Enterprise Linux ES 2.1 Samba 2.2.7 OpenLDAP 2.0.25 I followed the Idealx.org howto to build Samba+LDAP. I have a functioning, replicating domain on my lab workbench right now. Then I began to explore permissions on local shares, etc. when I discovered that to a Windows client, the only domain groups that are available from a Samba PDC are "Domain

Hi All, A couple of days ago I posted a query here about the loss of performance on my backup server after I moved from Red Hat 7.3 to SuSE 8.1. It appears as though, with no hardware or script changes, that my backup process takes 4 hours longer with SuSE 8.1. I'm doing (what I think is) a very simple script that basically employs SMBMOUNT, CP, and DIFF. Like this:

Four years ago, I migrated our network from Windows NT based servers to Linux, Samba+LDAP based setups. This setup has worked fine. Last year, we replaced our Exchange 5.5 server - the last "real" Windows server - with Scalix. This last decision has come back to bite me. Several new "thingys" that the boss wants, among other things, are forcing me to implement Exchange

Andrew Barlett wrote: > > Domain trusts (in terms of us being a PDC trusting other DCs) are > currenetly a work in progress. We hope to have it finished for Samba > 3.0. > > However, why do you need domain trusts? (There are lots of > good answers > to this question, but make sure you do have one of the answers). > > Samba 2.2 has always supported being a member

I've got a Samba (3.0.14a) controlled domain that contains 1 Windows 2003 Server as a member server. I've been thinking about using Terminal Services from that machine to allow roaming users (ie, those outside of the office) to connect to our network and get work done. My only concern at this point how to deal with the lack of an Active Directory and still allow Terminal Services to

Steven Langasek wrote: > Having one PDC and two BDCs also gives you greater > fault-tolerance than > having three domains with a single PDC each. > > Samba+LDAP can give you this fault tolerance; it can't give you trust > relationships today, without a lot of finagling. > > Steve Langasek > postmodern programmer > Steve: I understand the role of/need for the

That was a good hint! Yes, I've installed SP2, and it realy seems to be the Problem. Now I've checked that on a machine with SP1 - and the jobs from the same printqueue are removed correctly there! -------- Original Message -------- Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? (14-Dez-2004 19:13) From: novosirj@umdnj.edu To: t.pompe@architekt-prinz.at >

I'm trying to migrate my existing RedHat ES Samba PDC to Ubuntu. The RedHat version of Samba is 3.0.9 and the Ubuntu version is 3.0.14a. Everything was going fine until I tried to import the LDIF of the existing LDAP directory. The LDIF actually imports all of the structure (OU and Group definitions) and all of my users, but it fails when it comes to my first machine account with this

Hi, I want to set up SaMBa PDC and BDC with LDAP. I read the TOSHARG2, but don't understand something: >Samba-3 cannot participate in true SAM replication and is therefore not able to employ >precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will not create >SAM update delta files. Ok, I understand until that, but: >It will not interoperate with a PDC (NT4 or

When BDC will not make any changes in ldap, is it safe to not set any *script paramater in smb.conf? --beast

hello I've been reading the thread (http://marc.theaimsgroup.com/?t=113286376900001&r=1&w=2) and I have the same limitation with WINS in a PDC/BDC. That's why I have the following (experimental) setup: PDC ==> wins support = yes, passdb backend: master ldap BDC ==> wins support = yes, passdb backend: slave ldap I configured some of my XP clients to use both WINS servers

Dear Help, We are currently running Samba 3.0.22 on a distributed network/domain as a PDC (primary domain controller) and several as BDCs (Backup domain controllers) in our branch offices located around the country. At this point, the PDC is set up in our corporate office (where I'm located) and users have no trouble authenticating (via logging into windows and accessing shares) and also

How much of a resource hog is a PDC? My understanding is that authentication is done vs a BDC if available. I configured my new file server as the domain PDC because I figured it would already have to run samba. I have two other machines configured as BDCs to serve as logon servers. I'm looking for opinions on whether I'm asking for performance problems by making my file server the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Sorry for this general question, but I'd like to hear your opinion on this subject, but I'd like to set up a really working backup solution for my PDC, currently it uses NFS, so there are lots of issues: No ACLs, When NFS server goes down, everything fails. What method would you recommend for replicating folders, keeping existing ACLs