samba - May 2005 - [Nearly Resolved] Samba-3 by Example, Ex 2.4

OK, I've got this one working, but only by enumerating the valid users in 
the "files" share--%S wouldn't work in the valid users field
(e.g.,
"smbclient //<servername>/files" would simply give an 
NT_STATUS_ACCESS_DENIED error).  This would be OK for a small LAN, but for 
small enterprises or LANs with 75-100 users, as some on this list have 
mentioned, that becomes cumbersome (would the field even hold 75 names?).

So now my question is this, since it appears I still don't have my users 
entirely correctly configured: %S, per the smb.conf man page, is the 
service name (files in my case) and not the user name--but the man page 
goes on to say that the %S macro attempts to deduce the user name from the 
service name. How does the macro attempt to do this?  Failing that, are 
there any ideas about what I'm still doing wrong in configuring my 
users?  The relevant parts of my smb.conf file follow.

Thanks for your help.

Eric Hines

[master]
         comment = Master work area
         path = /archive
         valid users = mfwic
         read only = No

[files]
         comment = The actual backups
         path = /archive/%U
         valid users = annlee, ehines
         read only = No


Out of the argument with ourselves comes poetry, out of the argument with 
others comes politics.
         --Yeats

Eric,

Are you working from the printed version of the book?
Are you working from the update that is on the Samba web site?

What version of Samba are you using?

If you are using a version more recent than 3.0.7 I suggest you use the book 
"Samba-3 by Example" from:

	http://www.samba.org/samba/docs/Samba-Guide.pdf

If you refer to the WHATSNEW.txt file that ships with your version you can see 
what changes were made that may explain why %S does not work.

- John T.

On Saturday 07 May 2005 16:17, Eric Hines wrote:
> OK, I've got this one working, but only by enumerating the valid users
in
> the "files" share--%S wouldn't work in the valid users field
(e.g.,
> "smbclient //<servername>/files" would simply give an
> NT_STATUS_ACCESS_DENIED error).  This would be OK for a small LAN, but for
> small enterprises or LANs with 75-100 users, as some on this list have
> mentioned, that becomes cumbersome (would the field even hold 75 names?).
>
> So now my question is this, since it appears I still don't have my
users
> entirely correctly configured: %S, per the smb.conf man page, is the
> service name (files in my case) and not the user name--but the man page
> goes on to say that the %S macro attempts to deduce the user name from the
> service name. How does the macro attempt to do this?  Failing that, are
> there any ideas about what I'm still doing wrong in configuring my
> users?  The relevant parts of my smb.conf file follow.
>
> Thanks for your help.
>
> Eric Hines
>
> [master]
>          comment = Master work area
>          path = /archive
>          valid users = mfwic
>          read only = No
>
> [files]
>          comment = The actual backups
>          path = /archive/%U
>          valid users = annlee, ehines
>          read only = No
>
>
> Out of the argument with ourselves comes poetry, out of the argument with
> others comes politics.
>          --Yeats
-- 
John H Terpstra, CTO
PrimaStasys Inc.
Phone: +1 (650) 580-8668

Author:
The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556
Samba-3 by Example, ISBN: 0131472216
Hardening Linux, ISBN: 0072254971
Other books in production.