RiseT

Thanks for your input, but in this case the answer is no, since I'm running FritzOS v07.19-74610 beta, and one of the new features of this beta is SMB3 (see here). The issue is only present for files that were stored on the FritzNAS prior to updating to the beta (and thus prior to migrating to SMB3). Anything stored there afterwards has no problems. I think this is some bug in FritzBox's migrations process from SMB1 to SMB3, and thus I have filed an issue at AVM today. Personally, I don't have much...

I guess you're correct. Now, I've tried 2 things in Windows Exlorer: Copy & paste the problem database from FritzBox's storage to the local desktop Cut & paste the problem database from FritzBox's storage to the local desktop (No synching or KeePass involved at this point) (1) does work without any problem When doing (2), on the other hand, I'm getting a Windows error message that says that the file cannot be read ("Die Quelldatei oder vom Quelldatenträger kann nicht gelesen werden.") So this should...

I guess you're correct. Now, I've tried 2 things in Windows Exlorer: Copy & paste the problem database from FritzBox's storage to the local desktop Cut & paste the problem database from FritzBox's storage to the local desktop (1) does work without any problem When doing (2), on the other hand, I'm getting a Windows error message that says that the file cannot be read ("Die Quelldatei oder vom Quelldatenträger kann nicht gelesen werden.") So this should mean that this issue has nothing to do with...

If that's what you mean, I've replaced the new, working backup copy with the old, non-working one. Synchronizing still doesn't work with the old file (and still does work with the new one). I cannot see any difference regarding permissions; both files seem to have set the "archive" attribute only. Edit: I've just made an interesting observation, all done within Windows Explorer. I've moved the non-working database backup file from the FritzBox's storgage to some subfolder. Now, when I just MOVE (cut...

If that's what you mean, I've replaced the new, working backup copy with the old, non-working one. Synchronizing still doesn't work with the old file (and still does work with the new one). I cannot see any difference regarding permissions; both files seem to have set the "archive" attribute only. Edit: I've just made an interesting observation, all done within Windows Explorer. I've moved the non-working database file from the FritzBox's storgage to some subfolder. Now, when I just MOVE (cut & paste)...

If that's what you mean, I've replaced the new, working backup copy with the old, non-working one. Synchronizing still doesn't work with the old file (and still does work with the new one). I cannot see any difference regarding permissions; both files seem to have set the "archive" attribute only.

Related problem here with a twist. I'm on the latest FritzOS beta version (07.19-74610) which does support SMB3 (my Windows version is 1909). I'm using a trigger script in KeePass that synchronizes my database (local HDD) with a copy on the FritzBox's internal storage whenever KeePass saves the (local) database. With SMB1 I had not problems doing this, but since updating FritzOS and using SMB3, I'm getting the (German) Windows error message "Ein an das System angeschlossenes Gerät funktioniert nicht"....

Related problem here with a twist. I'm on the latest FritzOS beta version (07.19-74610) which does support SMB3 (my Windows version is 1909). I'm using a trigger script in KeePass that synchronizes my database (local HDD) with a copy on the FritzBox's internal storage whenever KeePass saves the (local) database. With SMB1 I had not problems doing this, but since updating FritzOS and using SMB3, I'm getting the (German) Windows error message "Ein an das System angeschlossenes Gerät funktioniert nicht"....