similar to: Integrating W2k3 Terminal Services w/Samba

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

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'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. My Situation: - One Machine with samba 3.0.14 acting as DC, DHCP3SERVER, BIND9 and dynamic DNS - One Machine with w2k3 server standard edition acting as DOMAIN MEMBER, TS and Citrix Access Essentials. - Domain Logons are working perfect. - Name resolving works fine. Reverse, Forward, NB, FQDN, IP ... - RDP Connection to the TS with local useraccount on the TS works fine - ICA Connection to

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

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,

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

hi, does samba 3.0.14 supports terminal server profiles? If not, is it planned? Regards, Alex -- ***************************************************** Alexander F?disch - Central IT Department- Max Planck Institute for Evolutionary Anthropology Deutscher Platz 6 D-04103 Leipzig Germany Email: foedisch@eva.mpg.de Phone: (+49) 0341 3550-168 Fax: (+49) 0341 3550-119

Are there any gotcha's..... I am currently using winbindd and very successfully integrating my Samba boxes with the NT4 domain structure. The admin who is doing the migration (A corporate person not used to Linux at all) is already nervous about the migration since it involves Linux. Usernames are not supposed to change..but, the authentication domain is going to be a completely new

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

Has anyone got this setup running? Can you point me to a HOWTO? I'm stuck with a problem in "smbldap_tools.pm" when I do any kind of basic thing. I keep getting this error: ============================================================================ == vulcan root # smbldap-usershow.pl Administrator Can't call method "search" on an undefined value at

I've been able to get PAM/NSS/LDAP working properly - silly typo. Still failing on the smbldap-tools use though. :( Kevin > > Has anyone got this setup running? Can you point me to a HOWTO? > > I'm stuck with a problem in "smbldap_tools.pm" when I do any > kind of basic thing. I keep getting this error: > >

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

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