Hey Jammie,

----- Original Message -----
From: "Hall, Jammie" <[EMAIL PROTECTED]>
Subject: Samba users


> 2.      issue #2 - user setup. do I have to setup each user this way.

That is one of the most important issues to consider when deploying samba.
As you need a samba _and_ a Linux-user for every Windows-user, there are
always two topics to think about; how do I manage the Linux (OS) -users and
how do I authentify the Windows-users. In short: How do I manage only _one_
userbase.

I presume you use a NT4.0 as a PDC, so I will go from there. You have the
following possibilities:

-Create every user as Linux and smbpasswd user like you have described. You
could write a simple shellscript to automate that task

-Create the Linux users and let the authentification go against your PDC.
You avoid the management of the samba users on the Linux/samba box. That is
the preferred way to get rid of the management of the smbpasswd file. In
smb.conf use "security = domain", "password server = <netbios_name_of_pdc>"
and let the samba box join your domain.

-Do the same as above and let samba create the Linux users when a user is
trying to get to a share. Like that: "add user script = useradd -d
/dev/null -s /bin/false %u" in your smb.conf. That will work for SuSE,
adjust for other distris. Every user successfully authentified against your
PDC will be created automagically as a Linux user.

-Use the winbindd daemon, included since 2.2, to get users from the PDC.
That is great! But use 2.2.3a due to memory leak in earlier versions.

-You could also use the NIS server included in the "Services for UNIX 2.0"
from M$.

By the way, there is a wealth of docs out there...read the samba
howto-collection, the online (or printed, of course...) version of "Using
Samba" from O4Reilly and the man pages.

Have fun,
Goetz

Reply via email to