When I'm on my Linux machine at home, I can scp files out of the box to remote locations without any problem. However, if I'm at a remote location, I cannot scp files into the box. Before you look at the output, I'm sure it's not a firewall issue. I SSH into the box every day without a problem, and the only reason it didn't ask for a password is because it is using DSA authentication. That being said, here is the output:

# scp <filename> <username>@<domain>:<path>
No value for $TERM and no -T specified
No value for $TERM and no -T specified
scp: warning: Executing scp1 compatibility.
scp: FATAL: Executing ssh1 in compatibility mode failed (Check that scp1 is in your PATH).
lost connection

This is just a default RH9.0 install, I believe. I have the same distro on a machine at work and have no problems scp'ing to that machine. What should I be trying to fix?

A couple of things to look at you can do ssh -v or ssh -vv and it'll show you the negotiations between the two servers. It might let you know where your connection is failing. At a guess, I would look at your authorized keys and make sure it matches the id_rsa.pub or identity.pub from your work system. (Or vice versa from your home system to your work system). Also make sure the user you're scp'ing into's home directory has only 755 permissions and the .ssh is set at 700 so you log in to your target system.

M. Lacy
Western Tool Supply.

Here is an output...

# scp -v <filename> <user>@<domain>:<directory>
Executing: program /usr/bin/ssh host ash-can.com, user <user>, command scp -v -t <directory>
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to <domain> [<ip address>] port <port>.
debug1: Connection established.
debug1: identity file /home/<username>/.ssh/identity type -1
debug1: identity file /home/<username>/.ssh/id_rsa type -1
debug1: identity file /home/<username>/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 134/256
debug1: bits set: 1625/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '<domain>' is known and matches the RSA host key.
debug1: Found key in /home/<username>/.ssh/known_hosts:1
debug1: bits set: 1603/3191
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /home/<username>/.ssh/identity
debug1: try privkey: /home/<username>/.ssh/id_rsa
debug1: try privkey: /home/<username>/.ssh/id_dsa
debug1: next auth method to try is keyboard-interactive
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is password
<username>@<domain>'s password:
debug1: ssh-userauth2 successful: method password
debug1: fd 4 setting O_NONBLOCK
debug1: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: Sending command: scp -v -t <directory>
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: rcvd eof
debug1: channel 0: output open -> drain
debug1: channel 0: rcvd close
debug1: channel 0: close_read
debug1: channel 0: input open -> closed
scp: warning: Executing scp1 compatibility.
scp: FATAL: Executing ssh1 in compatibility mode failed (Check that scp1 is in your PATH).
debug1: channel 0: obuf empty
debug1: channel 0: close_write
debug1: channel 0: output drain -> closed
debug1: channel 0: almost dead
debug1: channel 0: gc: notify user
debug1: channel 0: gc: user detached
debug1: channel 0: send close
debug1: channel 0: is dead
debug1: channel 0: garbage collecting
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 255
lost connection

are you using open ssh on both systems? it's posting something about incompatibilities so I'm wondering if one side or the other has been upgraded or modified to run something that emulates ssh rather than ssh.

Here are the ssh RPMs installed on two machines from which I've tried this:

openssh-3.5p1-11
openssh-server-3.5p1-11
openssh-askpass-3.5p1-11
openssh-askpass-gnome-3.5p1-11
openssh-clients-3.5p1-11

openssh-askpass-3.5p1-6
openssh-3.5p1-6
openssh-server-3.5p1-6
openssh-askpass-gnome-3.5p1-6
openssh-clients-3.5p1-6


Here are the ssh RPMs on the machine that seems to have the issue:

openssh-3.5p1-6
openssh-server-3.5p1-6
openssh-askpass-gnome-3.5p1-6
ssh-3.1.0-8
openssh-clients-3.5p1-6
openssh-askpass-3.5p1-6



The only thing I'm noticing is the ssh-3.1.0-8 RPM on the problem machine. It doesn't seem to be on either of the other machines, but that doesn't really mean anything to me.

>scp: FATAL: Executing ssh1 in compatibility mode failed (Check that scp1 is in your PATH).<

Do you have ssh protocols 1 & 2 enabled on the remote server?

Well, I ran the RH up2date thing on the problem box and I'm able to scp files to it once again. However, I am still getting those errors that say:

No value for $TERM and no -T specified

What do I do about these??




Thanks for all the help, by the way. I appreciate your time.