Wow where to begin here.
You complain that your distro didn't come with an AD compatable version of samba. Hmmm... the article was about using linux as a workstation. Samba is a software suite to allow linux/unix OS's to be Windows file servers. It is NEVER used to join a linux workstation to a Win2000 domain.
Firstly, samba was capabale of joining a Win 2000 domain as a member SERVER since 2000 came out, as long as the M$ server was running in mixed domain mode. As far as joining a non mixed domain, Samba has been able to be a member server in a M$/Kerberos/LDAP environment since version3.
Certainly this is not the easiest thing to do, but it's not impossible, and SAMBA's documentation is some of the best open source software documentation around.
This complaint only matters if you plan to share the drive on your WORKSTATION with windows users.
Further, it is hardly a complaint against linux, as Samba is a completely seperate project.
Secondly, if your complaint is that your linux WORKSTATION couldn't join the Win2000 domain for logging on to the linux box, there are a multitude of complexities here. One would need to set up Kerberos, an LDAP client and pam so that logins could bounce of M$ (in)Active Directory. Further, I'm not certain that that would be sufficient since linux/unix doesn't hash passwords like M$ does. I've not tried this yet. Time to head off to the server cave and give it a shot :).
That said, what would be the benefit? I'm unaware of an exchange client for linux that would use your unix login and kerberos ticket to contact an exchange server (is there a linux exchange client-don't use exchange myself?). The only benefit to this is if the W2000 domain policy does not allow non domain member computers to access server shares (ie, a windows XP home computer). However, accessing Windows shares on linux is either through smbclient, which I don't use, or a mount command, which I do use. However, I'm not certain that, even if the user login was authenticated off AD, that the machine itself could join the domain (hmm...maybe one WOULD use samba here.....). And I'm not sure that either mount_smbfs or smbclient would use the login ticket either.
As far as Samba version info, uh.... how about
riv2# smbd -V
riv2# smbd --help
Usage: smbd [OPTION...]
-D, --daemon Become a daemon (default)
-i, --interactive Run interactive (not a daemon)
-F, --foreground Run daemon in foreground (for daemontools
-S, --log-stdout Log to stdout
-b, --build-options Print build options
-p, --port=STRING Listen on the specified ports
-?, --help Show this help message
--usage Display brief usage message
Common samba options:
-d, --debuglevel=DEBUGLEVEL Set debug level
-s, --configfile=CONFIGFILE Use alternative configuration file
-l, --log-basename=LOGFILEBASE Basename for log/debug files
Or how about the old reliable RTFM...it's at <http://www.samba.org>
samba - A Windows SMB/CIFS fileserver for UNIX
The Samba software suite is a collection of programs that implements
the Server Message Block (commonly abbreviated as SMB) protocol for
UNIX systems. This protocol is sometimes also referred to as the Common
Internet File System (CIFS). For a more thorough description, see
http://www.ubiqx.org/cifs/. Samba also implements the NetBIOS protocol
Anyway, as a Windows and Samba domain admin, I just had to sound off on this little gem of a response. BTW I use linux rarely, I have a MASSIVE nvidia 7900 gtx sli'd dual core Windows gaiming PC, a really nice $1000 wide screen HP Windows laptop for travel (gotta play WoW at the hotel on the road you know) and another laptop running PCBSD for work in the office. I'm no eveagelist, and I enjoyed chronic's article. You use the OS you need to get the job done, end of story. But please don't confuse the OS with OSS that comes bundled with it. (BTW my servers are mostly FBSD but I have a Windows, Linux, and OSX server as well).