Hello,
Are I, Q and R drives are different to L?
Hi @RalphGL
Does your Windows user have write permissions on drive L? Or in other words: Can you create folders and files on this share directly via Windows Explorer? If not, the permissions on the SAMBA server are not set correctly…
In other words:
On the server in /etc/samba/smb.conf the share “Steuer” must contain the entry “ReadOnly = No” and perhaps a valid “Create Mask” - value.
Yep. But I don’t think it’s a permisson issue anymore. I tested this briefly on my Win10 machine and had the same exact issue. I have no idea what caused the issue, but after I unmounted the share and mounted it to another drive letter it worked. Then I changed it back to the original drive letter and it worked again. Btw… I deleted the account each time in the app and added it again after changing the drive letters…
@RalphGL Maybe this will help you somehow, although as I said I have no idea what exactly causes this issue…
this are different shares from the same samba server
As i have written above:
"
This is really strange.
I have tried to add a second share to a drive q:\othersubdirectorythansharedbefore and this was not possible. So the problem must be caused by a newer version of nextcloud. The old shares which was created one or two years ago ares still working. New shares are not possible.
I would like to reset all share-settings for this server and create them new. but uninstalling of the windows client does not help. After uninstalling and a new install the same (old) shares are there again. I think there must be some garbage - created from a prior version of the windows client. How can i remote this. A “purge” which removes all settings of the nextcloud windows client on the windows system would be fine.
Remove folder %APPDATA%\Nextcloud to remove all settings.
Docs: https://docs.nextcloud.com/desktop/3.3/advancedusage.html#configuration-file
1 Like
I just ran into the same problem using the current Windows Client (3.3.5 and a previos version; 3.3.x I guess): A folder located on a NAS/SMB/Samba share which is mapped to a local drive should be shared to a nextcloud instance. Windows itself can access the folder fine for reading and writing, however nextcloud reported missing write permission. The same configuration worked with previous versions. The problem also appears for SMB-Shares using different servers like Windows Server 2016, so the problem is most likely related to SMB itself, not Samba or Unix File Permissions. Deleting APPDATA%\Nextcloud did not help. Folders on local drives work fine. I hadn’t had the chance to test when this regression was introduced due to the need for reboots between downgrades, guell I’ll take a look at that in the following days.
Meanwhile I have installed the Nextcloud Desktop Client v. 3.3.5 on a Windows 10 and a new Windows 11 System.
Syncing samba shares is no more possible on this system too (and yes, all shares are writeable for the client user).
I don’t know, if it will work:
Before release of desktop client 3.x I prefered version 2.6.5:
https://download.nextcloud.com/desktop/releases/Windows/Nextcloud-2.6.5-setup.exe
Maybe it will work and then we will know, whether it is a software 3.x issue.
OK, found another system I could use for testing. Latest version supporting SMB-folders is 3.1.3. Versions >=3.2.0 (including rc1/rc2) do not work.
If I guess correctly there was no change in the code involved (desktop/folderman.cpp at 3c749bd3834f624f7270013218e9cf9cd572fb93 · nextcloud/desktop · GitHub), so it might be a bug in Qt, not NextCloud itself.
1 Like
I can confirm that with version 2.6.5 on the same Windows 8.1 system, synchronization with the same Samba shares is possible, but no longer with the current version 3.3.5.
So it seems to be an issue with desktop client 3.x or its library.
As said, 3.1.x works fine, so not a 3.x-problem, only 3.2.x and 3.3.x.
Since this is obviously a reproducible bug of the windows desktop client, there should be an issue on github.
I searched on Issues · nextcloud/desktop · GitHub and did not find this bug. Is this the right place and search phrase? Since I have no experience making new entries there and am not familiar with the desired procedure, it would be nice if someone who is more familiar with it would post the bug and then link it here. Can someone do that?
I have the same issue in client 3.8.0
it’s not working with SMB share on Windows 10 Pro.
Now i installed 2.6.5 and it works like a charm!
There is a BUG!
kindly
same for me with client 3.10.1 (x64)
quite the same configuration as the original description from RalphGL.
Hermann