Open GoogleCodeExporter opened 8 years ago
Wanted to report that I have the same issue.
What version of the product are you using?
win-sshfs: 0.0.1.5
Client OS: Windows 7 SP1 x64
Server OS: Mac OS X 10.9 Mavericks
Ssh server: OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
I can confirm that the connection isn't a problem, WinSCP is connected
correctly.
Also the error message above "could not connect: user authentication method is
not supported" is the error it gives consistently BUT, the first error that was
given several times before this CHANGED was "Hostname can not be resolved". I
hope this gives you clues on what is the source of the issue.
See Attached screenshot
Original comment by er...@secureapps.us
on 30 May 2014 at 8:43
Attachments:
I've tried both with hostname and with IP, both the same error, so I don't
think is a name resolution problem
Original comment by fdofo...@gmail.com
on 30 May 2014 at 10:56
Run as Administrator.
Original comment by monsoon...@gmail.com
on 20 Aug 2014 at 2:12
I hit the same problem in windows 8
Sshfs 0.0.1.5
Dokan 0.6.0.0
SSH.NET 0.1.0.0
Icons
The remote server is:
LSB Version:
core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64:desktop-3.1-amd6
4:desktop-3.1-noarch:graphics-2.0-amd64
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Server 10 (x86_64)
Release: 10
Codename: n/a
the remote server works without any problem, actually I sshsf from an Ubuntu
machine and it works as expected.
if you need any other information, pleas let me know, is a way to get some kind
of logging of what is hapening?
Original comment by mariog...@hotmail.com
on 7 Oct 2014 at 10:08
same here with SLES 11 sp3 and windows 7 64bit.
it seems the "authentication method not supported" is a common problem/bug.
i tried using multiple drive letters and multiple linux directories to mount.
neither "." nor "~" nor "/" worked so far using the simple "password" method. i
tested login with putty, a simple ssh client to test the user credentials ant
it worked fine. this sshfs client on the other hand throws this silly error
message.
Original comment by axel.werner.1973@gmail.com
on 10 Feb 2015 at 10:02
Original issue reported on code.google.com by
fdofo...@gmail.com
on 16 May 2014 at 8:49Attachments: