similar to: Samba and Word 2000 problems

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

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

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:

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

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

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've got a Red hat 8.0 machine running the latest "up2date" version of Samba (2.2.7 with Red Hat's patches) acting as a print server using CUPS. The printing of documents is fine for the most part. But I have noticed one thing that is really nothing more than an annoyance and was wondering if anyone else has seen the problem and possibly a cure. I have all Windows 2000 Pro

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

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

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,

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

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

I've had a Samba print server in my network for nearly 4 years now. The time has come for me to replace it with a more powerful machine. I have nearly 50 client machines (Windows 2000 and XP) attached to the printers that the existing server has and I don't want to have to touch them during this upgrade. I already have the new server built. Samba and CUPS are both ready for the

Appologies if this has been asked before, i have searched the archives and while there are some almost related issues, none really answer my question/problem. Recently (about 4 months ago) we purchased a new Dell 2600 (2.0Ghz Xeon 2GB Ram), Machine (single cpu) and migrated the data and system from rh 6.2 to 8 on this new server. By migrate i mean Installed rh8 fresh and moved the user data

I'm in the middle of Samba 3.0.9 ==> 3.0.14a migration testing. Because I'm using newer tools, I am also using a newer verions of the Samba LDAP Tools. My older version, 0.8.4, used the 'mkntpwd' utility to generate NT passwords. The new version, 0.9.1 defaults to using (what looks like) a Perl module called Crypt::SmbHash. My questions: Do I need to continue to use mkntpwd?