[ Thanks to Jeremy
Allison for this link. ]
“In this article, Daniel Robbins explains how Samba 2.2
improves on the already-excellent Samba 2.0.8 to create an
incredibly powerful enterprise-ready Unix/Windows integration
solution. The new Samba 2.2 offers a host of new improvements,
including Windows 2000 client and Windows NT domain controller
support, to name just a few.“
“If you’re like me, you’re very familiar with the incredible
importance of a particular piece of free software called Samba. For
years many of us have been using Samba valiantly to integrate Unix
and Windows systems into a single, unified networking environment.
We’ve successfully configured Samba 2.0.x to serve files and handle
print jobs for Windows machines, even to authenticate Windows
logins. And some of us have even been fortunate enough to get Samba
2.0.x to function as a Windows NT Primary Domain Controller, or
PDC, allowing a Linux or Unix server to act as a central control
point for an entire Windows NT domain. Yes, for the last few years,
the Samba 2.0.x series has allowed us to do a lot of amazing
things, which many once thought impossible.”
“Of course, if you’re familiar with the Samba 2.0.x series, you
also know that Samba has its share of limitations. Samba 2.0.x
veterans know that the key to a successful Samba installation is to
be keenly aware of these limitations and to work around them. As
long as Samba is used appropriately, it has proven to be a very
reliable solution, often much more reliable than Windows NT itself.
However, if you’ve ever used one of Samba’s less-than-stable
features, you may have easily created problems for yourself. Over
the past several years it has been these quirks that have made
Samba 2.0.x an almost perfect Windows/Unix integration
solution.”