Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Windows Books Media Operating Systems Software Unix Book Reviews

Samba 3 By Example 195

ALecs writes "When I first discovered Samba, I was in heaven! I could serve my Linux filesystems to my Windows 95 desktop and life was good. Between then and now, though, Samba has gotten a lot more capabilities, and I've been struggling to keep up with the cryptic voodoo that is Windows networking. While 'The Official Samba-3 HOWTO and Resource Guide' has been a great resource, Samba seems to just be once of those packages that you just need to see in action to understand. Hearing my cries, and those of countless others, John H. Terpstra has bestowed upon the Samba community the tome of ancient knowledge sought by all: Samba 3 By Example: Practical Exercises to Successful Deployment ." Read on for the rest of Malone's review.
Samba 3 By Example: Practical Exercises to Successful Deployment
author John H. Terpstra
pages 340
publisher Prentice Hall PTR
rating 10
reviewer Joshua Malone
ISBN 0131472216
summary Working examples to use Samba 3 in small or large office

Samba 3 By Example begins on a very friendly note by explaining how to get the most out of it any what you'll need to complete the exercises in the rest of the book. The beginning also includes a Windows networking primer, complete with packet captures (using the popular tool 'ethereal') showing how network browsing really works, under the hood.

This book follows the evolution of a fictitious company, "Abmas", through an impossible growth from a 9-person office to a 2000-person network with multiple sites around the world. You assume the role of the IT guy: charged with growing the company's network infrastructure, planning for change and, above all, keeping the users happy.

Some of the major challenges tackled in this book are:

  • Using Samba-3 as an NT-4 style PDC
  • Using Samba-3 as an domain member server
  • Using the various authentication backends as alternatives to the traditional 'smbpasswd' backend
  • Using LDAP to implement a Samba-3 PDC with backup domain controllers
  • Authentication using winbindd
  • Migrating from NT-4 to Samba-3 for a PDC
  • Using kerberos to integrate Samba-3 into a Microsoft Active Directory domain (as a domain member server)

I am extremely impressed by Terpstra's book. It addresses the complete spectrum of Samba deployments, from the 10-person office to the 2000-seat, multi-site enterprise while explaining not just what to do, but how to do it and, most importantly, why. The examples are practical and you can really imagine some poor sap^H^H^H^H^H^H^H^H unfortunate systems administrator finding him/herself in these very positions. This book says that these scenarios are hypothetical aggregations of real-world situations, but could swear I've worked for this company before.

One of the nicest things about this book is that each situation is followed by a Q&A section - almost like a textbook - that addresses both the important points of the exercise, as well as some of the trivial details that were left out for the sake of brevity. Don't be tempted to skip them thinking that it's just a rehash.

It's worth noting that this book is not a replacement for TOSHARG and defers to it for technical details in multiple cases. These two books should be sidearms for any IT administrator that has to deal with Windows clients on a daily basis.

I'm also very impressed with Terpstra's candor about Samba's features, weaknesses and road map. Nowhere in this book is Windows put down as inferior or is Samba touted as the "be-all, end-all" of Desktop and client management solutions. The relative flexibility of Active Directory and Samba is discussed only briefly and the choice to use Samba over Windows is ultimately left to the reader. Since you've gone to the trouble of purchasing this book, Terpstra assumes you've already made up your mind and require no further convincing.

Continuing to be mindful of office politics, Terpstra devotes a section in each chapter to the political implications of replacing Windows with an open source product, and an entire chapter to the issues inherent in bringing Samba into a traditionally Windows-based shop. Even though he refers to this chapter as a "shameless self-promotion of Samba-3", I found it to be an even-handed discussion of the issues you will most likely encounter from anti-Unix advocates and IT managers who have bought into the anti-Linux FUD. These are real issues that Systems Administrators need to know how to deal with effectively but too many of us simply dismiss because we feel they are uninformed.

In addition to examples of Samba configuration, examples are provided to integrate Samba with other useful servers such as the squid web proxy, OpenLDAP, bind and dhcpd. The configuration files for Samba as well as these additional pieces of software are also conveniently located on the included CD-ROM, along with Samba 3.0.2 packages for Red Hat Fedora Core 1 and SuSE Linux (Enterprise server 8 for x86 and s390 and SuSE Linux 9).

I think my biggest complaint with this book is that the "case study"-like format of this book tends to lump a large number of new features into a single example. This can make it hard to isolate the particular feature that you're interested in.

For instance, the example that illustrates automatic printer driver downloads to Windows clients is lumped into a chapter that is primarily concerned with using LDAP to implement a BDC. Automatic driver installation is a great feature that many sites far too small to consider implementing LDAP would likely be interested in.

In all, though, I'm extremely pleased with Samba 3 by Example - perhaps even more than TOSHARG. In it, you'll find plenty of tips, working examples and honest admissions of bugs (and their workarounds) that will keep you from losing your sanity. You could almost call this book a 300 page Samba and Windows networking consultant with over 8 years of experience. Terpstra has been incredibly kind to the Samba community by imparting so much wisdom to us all in this book.


Josh Malone has been a FreeBSD and Windows system administrator for three and a half years working in development shops and hosting companies, and currently works as a Linux engineer for an embedded systems company. You can purchase Samba 3 By Example from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page

This discussion has been archived. No new comments can be posted.

Samba 3 By Example

Comments Filter:
  • Re:Question: (Score:5, Informative)

    by jmays ( 450770 ) * on Wednesday April 21, 2004 @02:08PM (#8931581)
    It's a free, robust, easy to admin file server and DC with impeccable reliability.
  • Re:Question: (Score:3, Informative)

    by edk1 ( 58496 ) on Wednesday April 21, 2004 @02:12PM (#8931629) Homepage
    From what I recall, the file sharing benchmarks have proven to be faster, and best of all, no license fees for Windows Server. Also, the server itself will be immune to Windows viruses.
  • by blkwolf ( 18520 ) on Wednesday April 21, 2004 @02:16PM (#8931675) Homepage
    bookpool.com [bookpool.com]
  • by ALecs ( 118703 ) on Wednesday April 21, 2004 @02:18PM (#8931696) Homepage
    The most recent Samba-3 code now supports 'schannel' and "digital sign'n'seal" for joining an active directory domain. It cannot act as an ADS domain controller - only a member server
  • by lkaos ( 187507 ) <anthony@NOspaM.codemonkey.ws> on Wednesday April 21, 2004 @02:23PM (#8931748) Homepage Journal
    Samba can decode the PAC. I don't believe it actually using the information yet.

    This is because before using the information, you have to verify the signatures (to ensure the data hasn't been forged). Making use of the information in the PAC is on the TODO list though as it will result in a nice performance increase in some areas.

    And the PAC certainly doesn't violate any of the kerberos standards. Placing implementation specific information in the authorization data is what it's there for.
  • by ALecs ( 118703 ) on Wednesday April 21, 2004 @02:24PM (#8931762) Homepage
    I should also clarify that samba-3 can join as a Win2K member server and not just a legacy NT-4 server. The difference is in how you join the samba server to the domain.

    Use 'net ads join' to join as a Win2K member. If you use the older 'net rpc join' command, you're just doing NT-4 domain membership. Chapter 9 in the book covers Active Directory interoperation. The interoperability code is in Samba, not Kerberos.
  • by AmandaHugginkiss ( 756492 ) on Wednesday April 21, 2004 @02:26PM (#8931786)
    I just completed a three day training course based on this book. Every example just worked fine. The explanations are great but you do need the "Samba-3 Howto and Reference Guide" for detailed background information. I am happy that this book does not duplicate information. I manage a samba network and thought I knew a lot but this book has helped me to understand how much more I can learn and immediately use to make my users happier. I recommend this book to every network administrator.
  • Re:little known fact (Score:4, Informative)

    by amunter ( 313014 ) on Wednesday April 21, 2004 @02:28PM (#8931803)
    Yes, and at the recent FOSE expo in DC the Apple guy that was standing under the sign in the Apple booth that said "LDAP and Kerberos" showed me how easy it was to use.

    It uses all the normal Apple GUI type controls which basically take care of all of the configuration changes to smb.conf and krb5.conf. Basically a slick "apple looking" configuration file editor. I thought SWAT made samba configuration pretty easy, but this Apple stuff is great. Really cool stuff.
  • by Nighttime ( 231023 ) on Wednesday April 21, 2004 @02:30PM (#8931830) Homepage Journal
    This book is currently available through The Register's bookshop [theregister.co.uk] with 30% off to UK readers.
  • by Dimensio ( 311070 ) <darkstar@LISPiglou.com minus language> on Wednesday April 21, 2004 @02:32PM (#8931844)
    ...went back to 2.2.8a because for some reason it wasn't handling symbolic links properly. The drive containing the network share was running out of space, so I set up additional space on another drive and made a symlink to the location (yes, I used all lowercase letters in the symlink). Trying to access the directory with the 3.0.2a server resulted in a "Not a directory" error. It works properly in 2.2.8a, though.
  • by Anonymous Coward on Wednesday April 21, 2004 @02:49PM (#8932008)
    Actually, that's mostly not true. Windows 95 and 98 can join domains, and so can ME. It's Windows XP Home that doesn't have the domain logon feature.

    Businesses have been using Win95/98 systems on domains (Windows NT) and Netware networks for years. Windows ME can logon to and utilize an NT domain but there is no official Netware client for ME...not that I've heard of anyone using WinME with a Netware server.
  • by mangu ( 126918 ) on Wednesday April 21, 2004 @02:52PM (#8932040)
    it is very difficult to set up and make work correctly


    I recently upgraded two of my MS-Windows machines at home, put a GeForce fx5200 video card in my desktop and got a new HP/Compaq notebook with XP pre-installed. The main reason I still keep M$ machines is for games, and Need For Speed - Porsche Unleashed happens to be one of my favorites. It took me several weeks to get it working in the notebook, and it still doesn't work on the desktop.


    Compared to this, configuring Linux machines is easy. Usually you just need to look in the log files for error messages and paste the message text in a Google search to get the info you need to get it working.

  • by agrippa_cash ( 590103 ) on Wednesday April 21, 2004 @02:54PM (#8932062) Homepage
    I have been trying for MONTHS (on and off) to get SAMBA 3 working with LDAP. I got 2.2 working OK, so I'm not a complete idot. Still this book may be a good investment. For those who are interested the University of Navarra has a 3.0 HOWto and there is a 2.2 Howto (that I used sucessfully) at homex.subnet.at/~max/ldap.
  • by phallstrom ( 69697 ) on Wednesday April 21, 2004 @02:57PM (#8932114)
    http://www.oreilly.com/catalog/samba2/book/toc.htm l
  • by hot_Karls_bad_cavern ( 759797 ) on Wednesday April 21, 2004 @03:05PM (#8932199) Journal
    "I just completed a three day training course based on this book. Every example just worked fine. The explanations are great but you do need the "Samba-3 Howto and Reference Guide" for detailed background information...."

    That's funny, i just completed a google search for your "comment" here and gues what i found?

    VERBATIM COPY [amazon.com]

    Interesting.
  • by proub ( 26701 ) on Wednesday April 21, 2004 @03:12PM (#8932271) Homepage
    As linked in the article header, for one (not repeating in hopes people might seek out different mirrors). In general, head to http://samba.org/ [samba.org], find the mirror nearest you, and choose "PDF" or "HTML" from the "documentation" section's opening paragraphs.
  • by cloudmaster ( 10662 ) on Wednesday April 21, 2004 @03:18PM (#8932328) Homepage Journal
    WinME can authenticate against a domain, just as every (networkable) version of windows is able to. That login is then used when connecting to any network shares. Anyway, when the poster said "Domain Master" he probably meant "Browse Master", since what was the problems being caused were probably a result of browser elections, etc, and not domain logon issues.

    Every version of windows after Win 95 SP1 uses encrypted passwords by default. That includes WinME. You have to apply a registry change (documented in the docs/Registry/ directory of your samba source distro) to make them use clear text passwords.

    Linux authenticating against LDAP isn't very hard - most of the newer distros just require a couple button presses to set that up, and you should check out PADL's site (padl.com, IIRC) for scripts to migrate your /etc files to LDAP. Or check out my howto, which is generally near the top of a google search for "linux ldap authentication" or similar. Samba-to-LDAP is also easy, if you follow the step-by-step readme's that are all over the place (including examples/LDAP/ in the samba source distro).

    That 485 page PDF document bundled with the current Samba distro is really a useful read.

    BTW, calling people stupid doesn't help much, esp when you're wrong. ;)
  • by Mish ( 50810 ) on Wednesday April 21, 2004 @03:38PM (#8932515)
    The following settings resolved that issue for me:
    oplocks = no
    level 2 oplocks = true
    fake oplocks = yes
    Of course you'll want to RTFM on those commands first so you know what you're letting yourself in for. :)
  • by FyRE666 ( 263011 ) * on Wednesday April 21, 2004 @03:43PM (#8932564) Homepage
    fake oplocks = yes

    Erm, isn't that a completely insane thing to do (unless you're sharing a CD over Samba)?!!! The Windows clients will assume they have a lock on a file, and blindly write to it, even though other clients will assume the same! If you really are using this on a writable share and haven't clobbered a whole load of files, then you've been damned lucky!
  • by Dolda2000 ( 759023 ) <fredrik@dolda200 0 . c om> on Wednesday April 21, 2004 @03:51PM (#8932672) Homepage
    Seriously, Samba isn't easy to set up. I don't consider myself a lesser geek anymore, since I can set up virtually anything else I've tried without trouble (yes, that includes sendmail.cf), but I've more or less given up on Samba.

    Of course, the Samba developers shouldn't be blamed for that. I suppose that learning the black arts of Windows networking is about as logical as Windows itself, after all.

  • Re:Samba vs. NFS (Score:5, Informative)

    by Dolda2000 ( 759023 ) <fredrik@dolda200 0 . c om> on Wednesday April 21, 2004 @04:26PM (#8933015) Homepage
    Unfortunately, that's the case right now. NFS is supposed to be used in secure environments.

    However, that's going to change. There is already support for RPC security when using NFSv4 in Linux 2.6. That way, you can use Kerberos authentication and encryption for your NFS exports, and all is well. It's still marked as experimental, but I suspect it to be mature before long.

    All that already works on Solaris, of course.

  • by Etyenne ( 4915 ) on Wednesday April 21, 2004 @04:39PM (#8933204)
    According to Jeremy Allison, documentation for the PAC have been released by Microsoft, except the license to said documentation was too restrictive to be used by the Samba team.

    See http://linuxtoday.com/news_story.php3?ltsn=2000-05 -01-005-04-NW
  • by wackysootroom ( 243310 ) on Wednesday April 21, 2004 @04:45PM (#8933267) Homepage
    A better way to do it would be to only veto oplocks on certain types of files with the veto oplock files option.

    We had problems with dbase file locking until we vetoed oplocks on those files.

    To do it, it looks like this:
    veto oplock files = /*.DBF/*.dbf/*.CDX/*.cdx/*.IDX/*.idx/*.fxp/*.FXP/* .prg/*.PRG/*.mmo/*.MMO/

    This way, you're not using oplocks on only the types of files that are giving you hell, while getting the best performance possible from all other file types.
  • by Anonymous Coward on Wednesday April 21, 2004 @04:50PM (#8933333)
    No, that's not how they work. Being compatible with the protocol doesn't mean you have to implement the handling code in exactly the same way. Besides which, the code injected via the vulnerability would only work on a Windows system as it would use Windows API calls.

    On the other hand, a multi-platform worm that is specifically designed to target Samba and Windows networking vulnerabilities is quite possible.
  • Agree with reviewer (Score:3, Informative)

    by Etyenne ( 4915 ) on Wednesday April 21, 2004 @04:55PM (#8933383)
    My boss brought back a copy of S3bE from Real World Linux Expo in Toronto (with a dedicace to my name ... w00t!), and I must say I agree with reviewer. So far, I have only read chapters 10 and 11 (but thumbed through the rest), and they alone are worth the price of the book.
  • Re:Samba vs. NFS (Score:3, Informative)

    by slide-rule ( 153968 ) on Wednesday April 21, 2004 @05:10PM (#8933534)
    You implied work/office, but on my home LAN of 3 machines (two dual' into '98), I gave up on NFS and went fully-samba. I might not have had NFS *properly* config'ed through and through, but my home network is fairly simple. Still, I'd have occasional problems with NFS/automount hanging up somewhere causing machines to *not* be able to shutdown properly. (It'd hang the shutdown scripts.) Since I went all-samba (even for the all-Linux aspect of the network) this just doesn't happen to me anymore, so samba/automount seems more tolerant of oddball problems. (YMMV)
  • by janhct ( 585508 ) on Thursday April 22, 2004 @12:17PM (#8939827) Homepage Journal
    Guys,

    I committed the entire text of the book to the public samba-docs code tree on April 5th. We are having some difficulty in building the PDF file on the Samba build system. This will be resolved as soon as possible.

    We are committed to open information about open source software. Please be a little patient with us, you will get your candy soon.

    Cheers,
    John T.

To the systems programmer, users and applications serve only to provide a test load.

Working...