I am going to tell you something I always do as a matter of course when I set up a share in samba. I don’t know how it works, but it seems to get rid of permission problems for me. It may represent some other kind of security breach which , for others with more security-based needs, may not a be a good idea. But, it works for me and, as I said, I always use it. You may also wish to try it out:
Open Caja and navigate to “etc/samba”
Inside there is a file called “smb.conf”. Before you do anything else, right-click it and select “properties” and select the “opens with” tab. Inside there, ensure Pluma is the default program to open a file of this type with. Then close the properties dialog box.
Now, right click the file and select “open as administrator”. The file will now open in Pluma with full editing-rights.
Scroll down to the bottom of the file and you should see your recently added Samba entry. When you find it, add the following line to the bottom of the entry
force user = username
Where “username” is your actual username.
So, for example, mine would read as:
force user = stephen
See below for an example Samba entry with this additional line:
[stephen]
path = /home/stephen
writeable = yes
; browseable = yes
guest ok = yes
force user = stephen
When you are done, save and close “smb.conf”.
Then restart samba.
Now try and access the share again and see if your original problem persists.