Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Incompatible with freesshd

So it does not look like a WinSCP problem. Actually we do not have a good experience with freeSSHd.
sevaa

Re: Incompatible with freesshd

Hm, tried with psftp, not really. `ls` gives nothing but "." and "..". If I try "cd c:\", I get an error: "Directory /c:\: bad message".

Freesshd reports the current directory as "/", so one assumes its path system is somewhat unixy, but it's entirely unclear how do those unixlike paths map to the server's Windows style filesystem.
martin

Re: Incompatible with freesshd

Can you see the files using any other SFTP client?
sevaa

Incompatible with freesshd

WinSCP 5.17.7 on Windows 10, connecting to a freesshd ( http://www.freesshd.com/ ) server on Windows 7 over SFTP using key based auth. I can connect fine, but the folder appears empty. The current path shows up as /, which is wrong. You can't change directories manually, because WinSCP prepends all paths with /.

In the list of options for server shell in the connection properties, there's no way to specify cmd.exe, which would be the right one in this case.