Prev: Printing Problem with Samba ' Failed to allocate a print job'
Next: PDC migration: printing trouble. Summary.
From: Alex Harrington on 9 Apr 2008 10:50
> However, the @estero group cannot access the share at all
> (NT_STATUS_ACCESS_DENIED). What am I doing wrong?

Most likely the filesystem permissions prevent users in @estero from
executing or reading the /home/samba/lab_smb folder and/or the files in
it.

Cheers

Alex
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Luca Ferrari on 10 Apr 2008 06:30
On Wednesday 9 April 2008 your cat, walking on the keyboard, wrote:
> > However, the @estero group cannot access the share at all
> > (NT_STATUS_ACCESS_DENIED). What am I doing wrong?
>
> Most likely the filesystem permissions prevent users in @estero from
> executing or reading the /home/samba/lab_smb folder and/or the files in
> it.

Uhm..I've checked the file permissions, and since they are 777 I guess this is
not the problem. Moreover, since I've got a NT_STATUS_ACCESS_DENIED I think
that it is something that prevents users to access the share at all.
Any suggestion?

Thanks,
Luca
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Luca Ferrari on 11 Apr 2008 09:50
On Thursday 10 April 2008 Luca Ferrari's cat, walking on the keyboard, wrote:

> Uhm..I've checked the file permissions, and since they are 777 I guess this
> is not the problem. Moreover, since I've got a NT_STATUS_ACCESS_DENIED I
> think that it is something that prevents users to access the share at all.
> Any suggestion?

It is strange, this is the definition of the share:

[LABORATORIO_SMB]
comment = Cartella privata Laboratorio
path = /mnt/samba/lab_smb
browsable = yes
available = yes
valid users = @laboratorio @estero luca.ferrari
write list = @laboratorio
read list = @estero luca.ferrari
writable = yes
printable = no
force group = laboratorio

where I've added myself to the valid and read list. Then I forced a reload of
the configuration:

root(a)sede:~# /etc/init.d/samba reload
* Reloading /etc/samba/smb.conf...

but if I check the configuration with testparm I got:

[LABORATORIO_SMB]
comment = Cartella Laboratorio Sassuolo
path = /mnt/samba/laboratorio_smb
valid users = @laboratorio
read list = @estero, luca.ferrari
write list = @laboratorio
force group = laboratorio
read only = No

as you can see the luca.ferrari user is not added to the valid users list!
This could be the problem that such user always gets a
NT_STATUS_ACCESS_DENIED???
Any suggestion?

Thanks,
Luca
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Frank Weißer on 11 Apr 2008 15:00
Luca Ferrari schrieb:
> valid users = @laboratorio @estero luca.ferrari

from man smb.conf:

Example: valid users = greg, @pcusers

Did you try comma-separating all entries?

readU
Frank
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Chris Smith on 11 Apr 2008 17:20
On Wednesday 09 April 2008, Luca Ferrari wrote:
> [LABORATORIO_SMB]
>         comment           = Cartella privata Laboratorio
>         path              = /mnt/samba/lab_smb
>         browsable         = yes
>         available         = yes
>         valid users       = @laboratorio @estero
>         write list        = @laboratorio
>         read list         = @estero
>         writable          = yes
>         printable         = no
>         force group       = laboratorio

Try:

[LABORATORIO_SMB]
comment = Cartella privata Laboratorio
path = /mnt/samba/lab_smb
browsable = yes
valid users = @laboratorio, @estero
write list = @laboratorio
read only = yes

--
Chris
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
 |  Next  |  Last
Pages: 1 2
Prev: Printing Problem with Samba ' Failed to allocate a print job'
Next: PDC migration: printing trouble. Summary.