similar to: Upgrade from 3.0.2 --> 3.0.7

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

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

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

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

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

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

I have three users that are having trouble with my Samba network. This trouble is composed of two (possibly distinct) issues. My network is controlled by a Red Hat ES 3 server running Samba 3.0.2 with an LDAP backend. Issue 1: Laptop users, with "Offline Files" that are made of their "My Documents" directories. These directories are stored on the Samba server (so they can

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

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 modified the CUPS access rights (defined in cupsd.conf). Before that only users of administrative group had access to the printer configuration parts. Now I removed all access restrictions, so that anyone can access all CUPS services (printers, jobs, ...) (we use this, because sometimes we need to hold printers manually ...). But, as I mentioned, I don't find the relationship between this

Hi, I have a smb pdc running which works quite well so far, and would like to know if this feature is possible. I have two locations, and I want all users to authenticate on Machine A. Howver there are some users that are closer to machine B, and I would like to be able to have the homes of those users on machine B rather than machine A (they should authenticate on machine A anyway). Is this

We have about 50 CentOS servers with software RAID level 1 (mirroring). Each week, we swap out one of the drives (the one in the second of four hot-swap bays, only the first two of which contain drives) on each server and take them offsite for safekeeping. The problem is, the kernel seemingly randomly switches between /dev/sdb and /dev/sdc for these devices. This makes the process slower by

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

Hello, I've upgraded from 2.3.1 to 2.3.2. I've been used to list all mount points by <xsl:for-each select="source"/> under /icestats. Howver now the /icestats elemets contains only source elemets which have been requested at least once. That means the list (e.g. /stats.xsl under web directory) is empty after server start. I've found out this regresion presents only

I have a function like this: changedir <- function(dataframe) { dir <- dataframe$dir gc_content <- dataframe$gc_content d <- ifelse(dir == "-", gc_content <- -gc_content,gc_content <- gc_content) return(d) } The goal of this function is to be able to input a data frame like this: > lala dir gc_content 1 + 0.5 2 - 0.5 3 +

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 >