Prev: Error with boot-archive - Machine completely corrupted
Next: Need the Solaris SPARC patch 119254 (see body for other Solaris versions)
From: Jim Leonard on 3 Sep 2009 08:29 On Sep 1, 1:54 pm, Patata Kid <n...(a)none.com> wrote: > Can someone help me to resolve this mystery? Run a copy sshd on its own port in debugging mode, like: sshd -d -p 1234 This will sit there instead of going into the background. Then, try your SCP to the port (in the above example, port 1234 instead of 22). You'll see debugging messages scroll on the screen which will help you debug the problem. I think your sshd is only allowing Protocol 2 (which it should!) and that your winscp only does protocol 1.
From: claus.kick on 3 Sep 2009 08:53
On 3 Sep., 14:29, Jim Leonard <mobyga...(a)gmail.com> wrote: > I think your sshd is only allowing Protocol 2 (which it should!) and > that your winscp only does protocol 1. WinSCP does allowe for Protocol 2, I think the default setting is 1 only. |