Hey guys,
it's me again ...
I have a SMB Share in a jail on a ZFS Dataset.
Linux has write access. Windows 10 has not.
Samba server (v. 416) is running. All files are 777. ZFS is set on POSIX. Only the owner of a file has write access in Windows 10. Not group or other.
Is this a implementation issue with Samba? I am out of ideas.
Please share if you still have one. Thank you very much.
it's me again ...
I have a SMB Share in a jail on a ZFS Dataset.
Linux has write access. Windows 10 has not.
Code:
[global]
dns proxy = No
aio max threads = 2
max log size = 5120
load printers = No
printing = bsd
disable spoolss = Yes
dos filemode = Yes
kernel change notify = No
server multi channel support = No
nsupdate command = /usr/local/bin/samba-nsupdate -g
unix charset = UTF-8
log level = 1 auth_json_audit:3@/var/log/samba4/auth_audit.log
obey pam restrictions = False
rpc_daemon:mdssd = disabled
rpc_server:mdssvc = disabled
logging = file
server min protocol = SMB2_02
unix extensions = No
restrict anonymous = 2
server string = FreeBSD Server
bind interfaces only = Yes
netbios name = freebsd-nas
netbios aliases =
server role = standalone
workgroup = WORKGROUP
idmap config *: backend = tdb
idmap config *: range = 90000001-100000000
registry shares = yes
include = registry
vfs objects = zfsacl
[trans]
comment = Shared Folder
path = /mnt/data/trans
valid users = user1,user2,user3
write list = user1,user2,user3
browsable = yes
writable = yes
create mask = 0777
force create mode = 0777
directory mask = 0777
force directory mode = 0777
Samba server (v. 416) is running. All files are 777. ZFS is set on POSIX. Only the owner of a file has write access in Windows 10. Not group or other.
Is this a implementation issue with Samba? I am out of ideas.
Please share if you still have one. Thank you very much.