[Samba] Re: Samba access denied or only shows top level directories

[Tom Schaefer]

Oops, you know what, I was wrong.  When I wrote that I was thinking that when you force a user the group of the connecting user was retained but I just checked the smb.conf man page just now, which I should have done before posting my message and found this paragraph regarding force user:

In Samba 2.0.5 and above this parameter also causes the
          primary group of the forced user to be used as the pri-
          mary group for all file activity. Prior  to  2.0.5  the
          primary group was left as the primary group of the con-
          necting user (this was a bug).

In my smb.conf I do a force user on a bunch of shares and also force the group to that of the connecting user (force group = %G), strange as it may sound thats what suites my needs. I was thinking it happened by default.  Sorry, apparently it was only the default prior to 2.0.5 and then it was considered a bug.

None the less though, I'd pay really close attention to the permissions on those directories, so often in UNIX land seemingly weird problems turn out to be simple permissions issues.

Tom Schaefer

On Tue, 15 Apr 2003 09:30:09 -0500
"G.J.Francis" <G.J.Francis at open.ac.uk> wrote:

> RE: Samba access denied or only shows top level directories
> 
> Thanks Tom,
> 
> Im going to give the force groups a try , I actually meant smb.conf.mydev
> 
> Thanks for the suggestions
> 
> Geoff
> -----Original Message-----
> From: Tom Schaefer [mailto:tom at umsl.edu]
> Sent: 15 April 2003 14:31
> To: G.J.Francis
> Cc: samba at lists.samba.org
> Subject: Re: Samba access denied or only shows top level directories
> 
> Cool, somebody else besides me putting some of the more exotic features of
> samba to use, like the include = /opt/samba/lib/smb.conf.%L and the force
> user.  I do those same things myself, I use force user extensively, and
> sometimes I feel all alone in the world. 
> 
> Anyway, to your problem though, my first thought was its a permissions
> problem and that error message "file does not exist" isn't a very accurate
> error message.  In my experience, explanations given in Windows error
> messages may or may not bear any resemblence to the real cause of the
> problem.
> 
> Are you sure smb.conf.webdev is ever being included?  In this line: include
> = /opt/samba/lib/smb.conf.%L the %L means the netbios name of the server and
> the only netbios names I see you using are peewing, accesslist, and mydev.
> (webdev is curiously absent)
> 
> I see you aren't forcing the group, the group is going to end up being
> wes64's default group (not wduser's).  Maybe its a group permissions
> problem?
> 
> Are the clients that do work Win95 as well?  Do maybe these directories he
> can't get into have really long names or weird characters in the names?
> 
> So, there you go, just a few things to think about.
> 
> Tom Schaefer
> 
> On Tue, 15 Apr 2003 13:51:05 +0100
> "G.J.Francis" <G.J.Francis at open.ac.uk> wrote:
> 
> >
> > When ONE PARTICULAR user connects to \\mydev\oubsgout
> > <\\mydev\oubsgout> the user (running win95) connects( from windows
> > explorer) but only sees top level directories in the share. Any ideas
> > as to why only one user should be affected?The network between the
> > client PC and the server checks out ok. When the user attempts to
> > expand one of these top level directories a messagebox appears stating
> > that the requested file does not exist.
> >
> > [global]
> >         security = DOMAIN
> >         workgroup = SERVICES
> >         password server = serv1 serv2 serv3
> >         encrypt passwords = true
> >         netbios name = peewing
> >        
> >         netbios aliases = accesslist mydev
> >        
> >         server string = Samba %v on (%L)
> >         socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> >         log file = /opt/samba/logs/%L.log
> >         log level = 3
> >         max log size = 512
> >         load printers = No
> >         guest ok = no
> >         browsable = yes
> >         include = /opt/samba/lib/smb.conf.%L
> >         comment = "\\%L\%S <\\%L\%S>  [%v]"
> >         oplocks = no
> >         mangled names = no
> >         preserve case = yes
> >         case sensitive = yes
> >
> > In the smb.conf.webdev file  we have:
> >
> > [oubsgout]
> >         path = /fs1/oubs-goutime
> >         valid users = wes64
> >         force user = wduser
> >         writable = yes
> >
> > Thanks
> >
> > G.j.francis at open.ac.uk
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
> >