I would like to validate against the "collective" that the following
points are true (or not).

This is Suse 9.0 with SP1 with Samba 3.0.

In order for a windows workstation (win2000) to be able to use Samba
(via Net Use in this case), the windows signon (say 'tommy') must be
added to Linux as a Linux user, Samba share and in the SMBPASSWD file
(using smbpasswd as the backend, no LDAP etc, yet).

Once the user is added, the user doesn't have to do a net use for its
own share, but can directly do a net use for someone else's share (if
the user knows the password of the share as defined in smbpasswd).

It seems like that is what happening.  I guess that is ok if it is.
But I hate adding in all these Linux users, Samba shares, and SMBPASSWD
updates for a bunch of users, just so they can use Samba.  Especially
adding them in as Linux users.

I can see adding in Samba shares for each Windows user that points to a
directory, in which case, the Net Use will not ask for a password
(Win2000 username = Samba Share name)...

Just trying to stream line this process so we don't have a lot of extra
work adding in users, or maintaining them.

thanks

Tom Duerbusch
THD Consulting

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to