In win10 from cmd line: "The service sshfs has been started" but no unit shows up in explorer...
After some tryouts I was able to make sshfs to (appearently) work on windows 10 with public key + password So the output of the following command from commandline:
"C:\Programmi\SSHFS-Win\bin\sshfs-win.exe" svc \sshfs.k[USER]@[HOST]![PORT] X: "localuser"
was
load pubkey "/cygdrive/c/Users//.ssh/id_rsa": invalid format Warning: Permanently added '[HOST]:[PORT],[...]:' (ECDSA) to the list of known hosts. Enter passphrase for key '/cygdrive/c/Users/***/.ssh/id_rsa': The service sshfs has been started.
But NO UNIT was mounted or at least showing up in explorer. Not even reachable by "X:" on the address line.
Please help: it was hard for me arriving to this point, and now I seem almost at the end of the route but something's still not working...
OK wait a moment!
THIS command works but IN PART:
"C:\Programmi\SSHFS-Win\bin\sshfs-win.exe" cmd -ofstypename=SSHFS -p [PORT] -o idmap=none -o umask=000 -o Compression=no [USER]@[HOST]:/ x:
Now unit X: was mount and it is actually available via command line. In fact:
C:\WINDOWS\system32>x:
X:>dir Volume in drive X: has no label. Volume serial number is: XXXX-XXXX
Directory of X:\
30/09/2020 17:26 <DIR> DATA_FOLDER 07/10/2020 15:55 <DIR> dev 0 File 8.192 byte 2 Dir(s) 28.803.919.872 byte free
But STILL the X: unit won't to show up in windows explorer and it sems not to be reachable by writing "X:" on the address line...
Any clue?!
BINGOOOOO!!!!
I was running the command via an elevated command line: that made the unit available only to admin user. So, in this case, via command line, as I was logged in windows via another user.
I tried the same command via an ordinary command line, and the mount unit X: now shows up in explorer!!!
Sorry for the useless request.
At least I hope this experience of mine can be useful to othe users!
Bye,
@Gianpietro72 do you maybe know how to see the unit as admin? I tried opening explorer.exe as admin but it still wasn't showing up
It may mean you just run cmd.exe under the user permission not the admin permission.