Re: scp problems between Solaris and Tru64

From: Nico Kadel-Garcia (nkadel_at_verizon.net)
Date: 05/22/03

  • Next message: NoSpam: "Dual Monitors" 
    Date: Thu, 22 May 2003 21:05:17 GMT

    gerryt@gtconnect.net wrote:
    > In article <3ECB2B25.6E4739BB@ntlworld.com>,
    > "Dr. David Kirkby" <drkirkby@ntlworld.com> writes:
    >
    >>"Casper H.S. ***" wrote:
    >>
    >>
    >>>>sparrow % scp -v atlc-4.3.0.tar.gz davek@dobermann:/tmp
    >>>>Executing: program /usr/bin/ssh host dobermann, user davek, command
    >>>>scp -v -t /tmp
    >>>>scp: warning: Executing scp1 compatibility.
    >>>>scp: FATAL: Executing ssh1 in compatibility mode failed (Check that
    >>>>scp1 is in your PATH).
    >>>>lost connection
    >>
    >>>I believe this message originates from the remote end.
    >>
    >>Yes, I've come to that conclusion too. But is my local Sun requesting
    >>protocol 1 - and if so why?
    >
    >
    > Maybe a version issue. Try using ssh instead (which you say does work
    > in a previous post):
    >

    There may also be multiple ssh and sshd daemons installed, along with
    some potentially odd settings in the config files for the sshd. I'd
    suspect the sshd operating on the target host is actually not the later
    installed OpenSSH version. If it's ssh-2.x from ssh.com, then it *will
    not operate* in ssh1 mode unless the ssh-1.x is pre-installed *before*
    ssh-2.x compilation. This bit of nastiness is why the OpenSSH with a
    single dual-protocol client and daemon is so much more supportable.

    Tell your ssh client to use SSH-2 by saying ssh -o 'Protocol 2'" and see
    what happens. And you need to make the *client* use protocol 2, not just
    the server.

  • Next message: NoSpam: "Dual Monitors"
    • Quantcast