Map Rclone webdav share as network drive

I can't map rclone share webdav as windows remote drive
rclone serve webdav share_name: --addr 80 --user user_name --pass password
ON WINDOWS
net user x: http://127.0.0.1 password /user:user_name /persistent:no

The purpose of this is to map a share without installing WinFsp . no admin rights available.
Or is possible to add beside the actual share ways a smb share that afterwards to be mapped as drive?

Rclone version:
rclone v1.58.0

  • os/version: Microsoft Windows 10 Pro 21H2 (64 bit)
  • os/kernel: 10.0.19044.1586 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.17.8
  • go/linking: dynamic
  • go/tags: cmount

hello and welcome to the forum,

i have done that, mapping a rclone serve webdav using net use

  1. need to use a rclone debug log.
  2. mapping to port 80 can be a problem on windows and there is no need for that.
    the rclone debug log would show that.

It is possible to give me the correct command to do that?
Thank you!

rclone serve webdav remote: --user=user --pass=pass
NOTICE: remote: WebDav Server started on http://localhost:8080/

net use z: http://localhost:8080 /user:user pass
The command completed successfully.

dir z:
 Volume in drive Z has no label.
 Volume Serial Number is 0000-0000

 Directory of Z:\

03/26/2022  06:50 PM    <DIR>          .
03/26/2022  06:50 PM    <DIR>          ..
               0 File(s)              0 bytes
               6 Dir(s)  48,795,553,792 bytes free

Thank you, great job!

I tried to run rclone with admin rightist and still doesn't work.
I'm getting all the time the System error 67 has occurred. error while I'm mapping the webdav.
The rclone is serve the webdav server ok, I'm connecting trough Mozilla and WinSCP .

oh, system error 67.
--- has nothing to do with admin rights.
--- has nothing to do with rclone.

the workaround can be found here.
doing so is a MAJOR security risk,

to help you, i did the workaround, just so i could get the above commands to work.
and then i immediately undid the workaround.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.