i've set this up for several clients. the base is to use samba and ldap
with the smbldap-tools to tie them together. the tools are used to
populate and maintain the user definitions - instead of 'useradd' you
run 'smbldap-useradd', instead of 'passwd' you run 'smbldap-passwd' and
so on. once the ldap db is populated, you can set up samba to lookup
everything in ldap, do roaming profiles, all that crap. you can also
configure pam to use ldap so *nix machines can auth against it.
combined with mounting /home via nfs, it works very well when dealing
with multiple servers. and of course you can set up other services like
postfix, courier, apache, etc to use ldap auth (or pam). at one client
i even have an openvpn server authenticating against pam, which in turn
points to ldap.
the thing is, it's not trivial to set up, and even a two hour class
would barely scratch the surface. but if you're willing invest the time
to learn the ins and outs of the various pieces it works extremely well.
jason
Greg Brown wrote:
I second that. The "everything server" running Linux in the small
business. Authentication, file sharing, etc, etc, etc.
On 5/20/06, Carl Crider <[EMAIL PROTECTED]> wrote:
I would love this one.
-Carl
On 5/20/06, Jim Ray <[EMAIL PROTECTED]> wrote:
>
> How about having a class on a drop in replacement for Microsoft Small
> Business Server? Exploris has excellent facilities.
>
> Regards,
>
> Jim
--
TriLUG mailing list :
http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
