SOLVED: Samba 3.0.0 Access Blues

[Gar Nelson]

Gar Nelson wrote:
> Charles Curley wrote:
> 
>> On Tue, Dec 23, 2003 at 11:35:53AM -0700, Charles Curley wrote:
>>
>>> I am taking a Samba setup essentialy unchanged from Samba on Red Hat 8
>>> (samba-2.2.7-5.8.0) to Fedora Core 1 (samba-3.0.0-15). I can use
>>> smbclient to access anonymous shares (i.e. those not requiring a
>>> password). I cannot use smbclient to access my home
>>> directory. Security is the default, user, and passwords are to be
>>> encrypted.
> 
> 
> [...]
> 
>> I finally found the problem. I had "valid users = %S" in the
>> configuration file, apparently figuring that Samba would expand the
>> %S. It does not. I changed it to "valid users = ccurley" and it
>> worked.
> 
> 
> Actually, this seems like a real problem.  I have 30+ users, each with a 
> home directory on my samba server. I have 3.0 on a test server now, to 
> get everything worked out before moving it online. Good thing, eh?
> 
> While your solution works for a single user, I'd still like to see the 
> question answered for a multiuser environment.

Dang, like you, I answered my own question. In looking at 
/etc/samba/smb.conf.rpmnew, in the [homes] share the example conf no 
longer lists any "valid users" line. The solution in a multiuser 
environment is to leave it out entirely.

I've tested it here. I can now log into my home directory via Windows, 
and I can not see anyone elses home directory.

The man page for samba 3 does reference using the %S macro, even though 
it does not seem to work.

So, going from Samba 2.2 to Samba 3.0, the home section should be 
something like;

[homes]
    read only = no
    browseable = no



Cheers,
Gar

-- 
   -=[ Any opinions expressed are my own. ]=-