I setup ZimaOS on my server. I enabled file sharing. I can easily access the server files from my Android phone with full read/write access. But in Windows it seems the only way I can access the server from the Windows File Manager is by allowing Guest Access (which I cannot remember where to find that setting) on Zima. But that only allows me to read the files. I do not have write access, so I can’t add, delete, or move files.
From Windows I can only manage the files on the server through the web interface, which is cumbersome.
Can someone please tell get full access in the Windows File Explorer?
I believe the issue happens because you are connecting from Windows as a Guest user. Guest access on ZimaOS only allows reading, so Windows will not let you add, delete, or move files.
To get full access, I think you need to sign in from Windows using a regular ZimaOS user account that has read and write permission on the shared folder. I suggest opening File Sharing settings in ZimaOS, selecting the folder, and confirming that your user account is enabled with full access.
If Windows keeps connecting as Guest automatically, I think you may need to replace that saved connection so Windows asks for your username and password again. Once connected with a proper ZimaOS user account, you should be able to write normally from File Explorer.
I don’t know how but as I was reading your response, a notification from the the ZimaOS Client just popped up saying my drive is now mounted. I just checked I do seem to have full read/write access from Windows File Manager! I didn’t touch anything. I have no idea how or why this happend. I just hope the setting stays.
Nice. I believe the Zima Client may have re-established the proper connection using your ZimaOS account rather than Guest, which could explain why write access suddenly appeared.
I think as long as the Client keeps the credential in place, your access should remain stable. If it ever drops back to read-only, I suggest checking File Sharing to make sure your user still has write permission, then reconnecting through the Client again.
Glad it’s working now. Let us know if anything changes.