Samba share used to work on Windows 10. I think this might be some kind of new Windows issue but I would like to make sure that my Samba configuration has no major problem:
[global]
protocol=SMB3
workgroup = WORKGROUP
passdb backend = tdbsam
wins support = yes
local master = yes
preferred master = yes
[document]
guest OK = no
comment = Dokument Samba Share
path = /_fsrv/document
browsable = yes
read only = no
create mask = 0755
force user = smbuser
force group = smbuser
No adjustments made. This worked for several months. What I did so far is a proper reboot of server and Windows … this solved problems before, but not this time.
Any suggestions before I approach Windows-Universe?
Thanks in advance.
So, just to clarify that you can access the share but just not write to it via the Windows host?
Please show us the results of
ls -l /_fsrv/document
Thanks for your reply. This problem vanished yesterday as mysteriously as it came. As I said, I did not touch anything (knowingly). I just checked the zypper history:
2022-10-24 07:35:34 | install | samba-libs | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-24 07:35:34 | install | samba-ad-dc-libs | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-24 07:35:36 | install | samba-client | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-24 07:35:38 | install | samba | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-24 07:35:39 | install | samba-libs-python3 | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-24 07:35:40 | install | libsamba-policy0-python3 | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-24 07:35:43 | install | samba-python3 | 4.17.1+git.270.17afe7cb6b-1.1
2022-10-29 08:08:22 | install | samba-doc | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:38 | install | samba-client-libs | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:38 | install | samba-libs | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:38 | install | samba-ad-dc-libs | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:41 | install | samba-client | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:43 | install | samba | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:45 | install | samba-libs-python3 | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:49 | install | libsamba-policy0-python3 | 4.17.2+git.273.a55a83528b9-1.1
2022-10-29 08:08:56 | install | samba-python3 | 4.17.2+git.273.a55a83528b9-1.1
2022-11-20 08:24:39 | install | samba-doc | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:43 | install | samba-client-libs | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:43 | install | samba-libs | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:43 | install | samba-ad-dc-libs | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:46 | install | samba-client | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:48 | install | samba | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:49 | install | samba-libs-python3 | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:50 | install | libsamba-policy0-python3 | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:51 | install | samba-python3 | 4.17.3+git.279.ff9bb8a298-1.1
2022-11-20 08:24:54 | install | yast2-samba-client | 4.5.2-1.1
I have the impression that this was sorted out with some changes made lately.