Mount a rclone and share it with windows

Hello, I want to munt a rclone and share this drive with windows, I want to access this drive from other windows on my local lan, can I do it??.

I mount with rclone mount drive2cifrado: Q: --vfs-cache-mode writes, but when I try to share the drive Q I cant...

And can I do it with linux?

Please help.....

Thanks.

hello and welcome to the forum.

yes, you can mount on linux, has you read this?
https://rclone.org/commands/rclone_mount/

are you able to access the q: drive?

have you look at the log file for errors?

hello , thanks, I can access to Q on windows, but I cant share...

you need to run rclone mount as system user and then share it.

Hello, and how do it?, I do it open a cmd and ejecute rclone mount ...

Thanks.

  1. make sure you are using the latest table version of winfsp, which is v1.6
    https://github.com/billziss-gh/winfsp

  2. there are a few ways to run a program as system user.

a. the easiest to use and test with it task scheduler.
create the task and run is as system user like this
you can run the tast via the gui of task scheduler or via command line

schtasks /run /tn "rclone\rclone-mount-system-user"

b. you can use sysinternals psexec

c. use nssm.

d. use advanced run or nircmd from the nirsoft, have over 100+ free utilities.

Hi. The shortest way uses to be the direct one.

Using the OS (Windows 10 Pro x64 in my case) menu shortcuts it's possible to share a mounted drive via rclone+winfsp+nssm (the last for mounting as a service):



image image

You can see two connections to the shared drive from another pc on the same local network.

Greetings!

The only way I know how to do this is to run rclone under the SYSTEM account.

This can be done a few ways:

  • By running the script from task scheduler using SYSTEM as the account
  • By doing basically the same thing using NSSM (an alternative to task scheduler basically that has some nice extra functions for robustness).
  • By using a Microsoft tool-pack called "PStools" (google it). One of these tools (psexec) allows you to basically log into CMD as the SYSTEM user if you are already an administrator. From there you can just run rclone normally. This is really nice to have for testing and debugging but it's not exactly user-friendly for an every-day use case, so the 2 first options are probably better practical solutions.

The reason this is needed is (as I understand it) a limitation in how Windows handles user-spaces. Any virtual mounts created on a user-level will not be visible to the system - and it is the system that is invoked to enable network sharing among many other things, so it will be confused and not see the path you are trying to share. Anything the system does is visible to users however, so if that is where you run rclone it will all work as expected.