samba - Nov 2023 - Unable to write to share having same name as directory?

Thanks for the reply ...

However, if I simply change the name from [console] to anything else (ie.
[testing] or [consoleS]) then it works perfectly.

The user definitely has permission which I've verified through SSH (and the
fact that changing the share nme also works).

On Fri, Nov 10, 2023 at 5:15?AM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Fri, 10 Nov 2023 09:47:12 +0000
> Luis Peromarta via samba <samba at lists.samba.org> wrote:
>
> > Interesting to see an attachment in this list ?
> >
> > LP
> >
>
> that interested me as well, normally I get the attachments because I am
> a team member, but if others are now getting them, I wonder if
> something has changed ?
>
> Anyway, reading the logs, it looks like the OP has a very sparse
> smb.conf:
>
> [global]
>         fruit:copyfile = yes
>         fruit:delete_empty_adfiles = yes
>         fruit:wipe_intentionally_left_blank_rfork = yes
>         fruit:nfs_aces = no
>         fruit:veto_appledouble = no
>         fruit:metadata = stream
>         idmap config * : backend = tdb
>         vfs objects = fruit catia streams_xattr
>
> [console]
>         path = /storage/console
>         read only = No
>
> And picking out lines from the logs shows this:
>
> ..............
> make_connection_snum: Connect path is '/storage/console' for
service
> [console]
> check_user_share_access: falling back to read-only access-evaluation
> due to security descriptor
> ..............
> ..........
> open_directory: opening directory aa, access_mask = 0x80, share_access >
0x3 create_options = 0x1, create_disposition = 0x2, file_attributes = 0x10
> mkdir_internal: failing share access console
> open_directory: unable to create aa. Error was NT_STATUS_ACCESS_DENIED
> ................
>
> It looks to me that perhaps the permissions on the share are not
> allowing access.
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On Fri, 10 Nov 2023 09:26:00 -0500
John Klimek <jklimek at gmail.com> wrote:
> Thanks for the reply ...
> 
> However, if I simply change the name from [console] to anything else
> (ie. [testing] or [consoleS]) then it works perfectly.
> 
> The user definitely has permission which I've verified through SSH
> (and the fact that changing the share nme also works).
> 
I have used shares with the same name as the directory, so it should
work. Have you tried running 'testparm -s' to check if there is
anything wrong with your smb.conf ?
Could there be a usershare with the same name ?

Rowland

PS please do not 'CC' me, just reply to the list.