I don't know how to fix your problem with your original SSH server, but now that you've switched to freeSSHd, you're having a different problem.
Unable to execute command or shell on remote system: Failed to Execute process
basically means that it's trying to execute dir
without a shell, which won't work. There is no dir.exe
on your PATH
; there's a dir
command built in to cmd.exe
.
In other words, it's the same problem you'd get trying to execute a bash builtin without the shell on a POSIX system. And the solution is the same: Execute the shell with dir
as a command.
The way to do that is:
cmd /c dir
There's a further bug you might have with freeSSHd, which does some fancy stuff trying to hide the differences between a cmd.exe terminal and a POSIX terminal that can cause you to get errors about "no console window found". Hopefully you won't run into that one; if you do, dig through the preferences, and there should be a checkbox to turn this stuff off.
And, now that I think about it, whatever reason your original ssh server was acting weird (running ksh or something), having it execute cmd /c dir
instead of dir
would work around that problem, too; worst-case scenario you'd be running an unnecessary shell-inside-a-shell, which is silly, but wouldn't break simple things like dir
.