Repository navigation
Cannot climb up directories in windows explorer #37
Description
For some reason, it seems that it is no possible to climb up folders when writing the address in the windows explorer address bar. For instance:
\\sshfs\username@linux-host!9999
takes to you the user's home directory, as expected, but:
\\sshfs\username@linux-host!9999\..\..
just takes you back to the "Network" place in windows 10, instead of climbing up two folders. Trying to use absolute paths:
\\sshfs\username@linux-host!9999\\media
does not work either, an error message saying that windows could not access that destination.
However, all these commands work if they are used when creating a new network drive.
Activity
billziss-gh commentedon Jul 4, 2018
The
\\sshfs\user@serversyntax is meant as a convenience. It is possible to use double dot..and double backslash\\to make SSHFS-Win access root or parent directories, but this is more of a hack.If you need access to root directories, etc. I recommend either enabling access to them through a user on the SSHFS server or by using the bundled
sshfsdirectly from the command line. Thesshfscommand is available under\Program Files\SSHFS-Win\bin\sshfs.exe.wonx commentedon Jul 4, 2018
Oh, ok. How would you use the sshfs command in this case?
billziss-gh commentedon Jul 5, 2018
Open a command prompt and issue something along the lines of:
See
man sshfsfor more options. Not all will work on Windows.OskarAtGitHub commentedon Jul 29, 2018
When running the second of these commands:
I get a
I have Putty also installed on a windows 7 system. Could this potentially be conflicting with the ssh command, as in the other reported "issues"?
Mapping the drive via windows explorer works fine.
billziss-gh commentedon Jul 29, 2018
When you type
where sshwhich ssh is being picked up?OskarAtGitHub commentedon Jul 30, 2018
This is what I get:
4O4 commentedon Jul 30, 2018
Putty is a standalone program, it doesn't come with it's own
ssh.exe. Yourwhereoutput looks fine. You have twossh.exes in PATH but SSHFS-Win is first on the list so it is the one that is used under the hood.Maybe try with some additional flags, you should get more verbose output from the ssh directly:
OskarAtGitHub commentedon Jul 30, 2018
Yes, I though as much from the output.
This is what I get from the higher debug level output:
I assume the "needpriv 0", is the problem. I have no idea what that means though :D
I do have whitelist firewall settings. But ssh is on it. And the network drive mapping works via windows explorer (without options).
4O4 commentedon Jul 30, 2018
OskarAtGitHub commentedon Jul 30, 2018
Do you mean the .ssh dir on the remote machine?
I can't find a .ssh dir on the local windows 7 machine. I don't even have a /home/[USER] dir when viewed in Cygwin. "which ssh" returns /usr/bin/ssh
Is this my problem?
4O4 commentedon Jul 30, 2018
Oh nevermind, it was just a blind guess. I assumed you have created the whole
/home/user/.sshtree in SSHFS-Win installation directory (because that's the only place where sshfs-win will look at) but that's clearly not the case.I don't think so. But let's try one more thing - test if you can connect by just plain ssh. Run
ssh.exe [USER]@10.1.1.1 -vvvfrom the SSHFS-Win install location (via PS or cmd) and then from Cygwin terminal (outside of the install location so it picks/usr/bin/sshinstead).BTW can you connect using Putty without errors?
OskarAtGitHub commentedon Jul 30, 2018
Ok, I think we're getting somewhere!
Running ssh from cmd works fine. But does give the:
debug2: ssh_connect_direct: needpriv 0Running ssh from cygwin (from /cygdrive/c/Program Files/SSHFS-Win/bin) gives the same error as above, but results in
ssh: connect to host 10.1.1.1 port 22: Operation not permitted...regardless of which directory I run the ssh command from.
edit: yes Putty works without problems. I can run remote X and everything.
4O4 commentedon Jul 30, 2018
Can you paste the exact output from both cases?
OskarAtGitHub commentedon Jul 30, 2018
from cmd:
OskarAtGitHub commentedon Jul 30, 2018
And from cygwin:
(not sure if it makes a difference or not, but result is the same with "ssh.exe")
4O4 commentedon Jul 30, 2018
Well, looking at the version strings (OpenSSH_6.1p1, OpenSSL 1.0.1c 10 May 2012) it appears that sshfs.exe is indeed using cygwin's ssh binary. Now when I think about it it's pretty obvious and logical - you're using sshfs.exe directly while only using sshfs-win.exe guarantees that the bundled ssh.exe is used instead of the random ones from PATH.
Why, however, is the ssh from cygwin distro throwing these erors? I have no idea but this binary is so old that it is not even worth debugging any further. You may try to update it if possible (IDK what is the latest version available there).
Although personally I'd just force sshfs.exe to use its bundled ssh.exe because we know it works well. While it's not pretty solution at all, it should do the job for now.
OskarAtGitHub commentedon Jul 30, 2018
Command results in:
read: Connection reset by peerCan't figure out how to get the -vvv to work.
billziss-gh commentedon Jul 30, 2018
@OskarAtGitHub is it possible to SSH into the server using the SSH that is bundled with SSHFS-Win?
Please try this from a normal command prompt and not a Cygwin prompt.
4O4 commentedon Jul 31, 2018
@billziss-gh yup, we've already confirmed it works correctly outisde of cyg term (#37 (comment))
OskarAtGitHub commentedon Jul 31, 2018
Some further testing from cygwin:
4O4 commentedon Aug 2, 2018
@OskarAtGitHub Sorry, the last command I typed is wrong because
/cygdriveis not really available in this minimal environment. Give this one a try instead. Use powershell or cmd.OskarAtGitHub commentedon Aug 4, 2018
Yes, that works! Huge thanks!
I'll try playing around with the options to see if I can work on some performance and access issues :)
OskarAtGitHub commentedon Aug 4, 2018
This must be the dumbest problem I've had so far.
But can't figure out how to "unmount" the drive when mounted like this. Windows explorer has it as a local "FUSE" drive, not a network "FUSE-SSHFS" as when using the explorer map drive.
Windows explorer doesn't show a disconnect option, and:
4O4 commentedon Aug 4, 2018