similar to: New Samba 3.0 Schema

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

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

> -----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

I have a Samba 2.2.7a PDC (with an OpenLDAP backend) that seems to be giving me trouble. Here's the scoop: I have Windows 2000 Pro clients running Word 2000. Over the past several days, a lot of them have had trouble with their documents - most of the time during a save. The most critical of these failures presents the following error message when saving: "Word has lost data due to a

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

Yesterday I started to build a test network to evaulate our planned move to Samba 3.0.14 and Debian. I started off by duplicating our LDAP directory. On the exisiting Samba PDC/LDAP master machine, I did: slapcat -v -l old.ldif I put the 'old.ldif' file onto a floppy disk, went to the lab's server and performed slapadd -v -l /media/floppy/old.ldif The process stopped on the

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

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:

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

Ok, after three more days of pulling my hair out, I'm still stuck. I've got what I think is the problem, but I'm sure how to fix it. I'm building a Samba PDC using the IDEALX.org HOWTO. I'm using samba 2.2.7 and openldap 2.0.27 that I compiled from the Red Hat Network. This is being built on Red Hat Enterprise Linux ES 2.1. Ok, So I get to the part of the HOWTO that

Hello Lads, Problem could be smbldap-tools, im using 0.97. I have manually set the sid on the bdc which seems to work. I am confused because I thought net rpc getsid stored the sid from the pdc on the bdc in secrets. I wasn't aware that net getlocalsid should return identical results on both pdc & bdc. Please explain this - why isnt the BDC obtaining the sid automatic as it should

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

Hello Lads, I have a PDC & BDC / Master & Slave; I regularly make backups of the LDAP database: Slapcat ¡Vv ¡Vl backupallusers.txt. Both my PDC & BDC have been rebuilt from scratch, I slapadd ¡Vv ¡Vl backupallusers.txt and I net set localsid domainsidhere for the PDC << I get that from the backupallusers.txt. Smbpasswd ¡Vw secret < on both PDC & BDC Net rpc getsid

About two weeks ago, I posted a message to the list describing an error that I've been getting with Word 2000 documents. The subject line of that mail was: "Samba 2.2.7a and Word 2000 = Corrupted (?) files"; I submitted it on 10/15/03. I've not heard from anyone with a response to that inquiry, so I'm yelling for help one more time. I've scoured Google, the

Hi All! Thanks to all of you that responded to my previous posts. I've gotten a lot more info now than I used to have! But I still have questions. The biggest right now is: Is there a way build up a Samba PDC as a direct replacement for an existing Windows NT 4.0 PDC? All the material I've found to date is written from a standpoint of creating a new domain as you create the Samba

I have a small test environment setup with the following: Server Red Hat Enterprise Linux ES 2.1 Samba 2.2.7 - built from source OpenLDAP 2.0.27 - built from source OpenSSL 0.96b - built from source Note: All packages were downloaded from the Red Hat Network as Source RPMs - as far as I know, these are the latest "red Hat approved" versions. I made the proper changes to the .spec

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

I've got a Red Hat Enterprise "ES" Linux Server running Samba 2.2.7a and OpenLDAP 2.0.27 as my PDC in my main office. I have on rare occasions gotten error messages from my users that seem to be tied to MS Office 2000 files (Word in particular) similar this: An error occurred while connecting P: to \\stargazer\projects. Microsoft Windows Network: The local device name is already

I have a problem on the two heaviest-used Samba servers in my company. They both are exhibiting the same problem, just in different ways. Stargazer is my "Main" File and LDAP directory server - it functions as the "PDC" for my network. It's running Red Hat Enterprise Linux "ES" 2.1, a recompiled custom Red Hat "ES" version of Samba 2.2.7 (to add LDAP

Is there a way - without killing off Samba - to force a rebuild of the WINS database that Samba is maintaining? I've got a couple of completely bogus entries in WINS and I need to get rid of them, but I can't take the Samba server down to do it. I'm hoping that I can issue a couple of commands and poof the WINS database is blown away and it starts to repopulate with good data. If I