It's curios. After some time without touching anything, I can directly access my new Seagate share as //ip.address/share, but still if the same is shared through my NWSP2 I can read it, but to write to it I receive an error saying I need the write permission.
In the samba cfg I set my user in the write list, no users in the read list. I tried setting the samba "read only" setting to "no" too.
In all cases I'm able to read it, but not write to it. With direct access I can correctly read/write.
Here is the definition of my extra share (manually changed my ip to xxx.yyy below):
- Code: Select all
[NAS-Seagate]
#comment = yourcomment
comment = NAS-Seagate (BlackArmor 220)
#path = /direct-usb/yourMountPointName
path = /share/1000/192.168.xxx.yyy-smb-public
#invalid users = root user1 user2 ....(all other username without a read or write access and keep root user in the list)
invalid users = root dummy
#read list = user_read1 user_read2 (all other read username)
read list =
read only = no
#write list = user_write1 user_write2 (all other write username)
write list = mdi hanna
printable = no
ea support = yes
# with samba4 version uncomment the following lines
vfs objects = catia fruit streams_depot
streams_depot:delete_lost = yes
fruit:resource = file
fruit:metadata = netatalk
fruit:locking = netatalk
fruit:encoding = native
Here is the mounted share in /share/1000:
- Code: Select all
drwxr-xr-x 2 root root 0 2000-03-02 14:41 192.168.xxx.yyy-smb-public