Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

scp error: ksh scp: not found lost connection

455 views
Skip to first unread message

anniesm...@my-deja.com

unread,
Mar 28, 2000, 3:00:00 AM3/28/00
to
Hi all,
I have been having problems running scp lately. When I run
scp file-of-hostA hostB:/remote/directory and got the error message:
ksh: scp: not found
lost connection
when scp run with the verbose on, it exit with code 127. I am
forced to use ftp which is a no no. Even with ftp, I could not
ftp from hostA to hostB. It seems that hostB deny all accesses
eventhough all accesses are allowed in its /etc/hosts.allow and
/etc/inetd.conf .
From hostA I run
tcpdmatch ftp hostB
hostA said access is granted but when i run ftp hostB, it says
access deny.
I have run scp as regular user and also as root with no success.
The user's account on hostA and hostB have the same ID, Shell.
Please help

annie


Sent via Deja.com http://www.deja.com/
Before you buy.

anniesm...@my-deja.com

unread,
Mar 28, 2000, 3:00:00 AM3/28/00
to

jose

unread,
Mar 28, 2000, 3:00:00 AM3/28/00
to
anniesm...@my-deja.com wrote:

> I have been having problems running scp lately. When I run
> scp file-of-hostA hostB:/remote/directory and got the error message:
> ksh: scp: not found
> lost connection

sounds like it is not in your $PATH. try giving the full path to the
executable, often /usr/local/bin/scp ...

if so, modify your PATH variable upon startup to add /usr/local/bin .

jose nazario jo...@biocserver.cwru.edu

Robert E. Van Cleef

unread,
Mar 28, 2000, 3:00:00 AM3/28/00
to

Another problem may be the default path built into the sshd on
the target machine. /usr/local/bin is not normally included.
You may need to recompile/reinstall the sshd.

Bob
--
><> ><> ><> ><> ><> ><> ><> ><> ><> ><> ><> ><> ><>
Bob Van Cleef, Member of Technical Staff (408) 734-8100
MicroUnity Systems Engineering, Inc. FAX (408) 734-8136
475 Potrero Ave., Sunnyvale, CA 94086 vanc...@microunity.com

maldata

unread,
Apr 1, 2000, 3:00:00 AM4/1/00
to

>
> Another problem may be the default path built into the sshd on
> the target machine. /usr/local/bin is not normally included.
> You may need to recompile/reinstall the sshd.

If we're talking about SSH2, then the problem I've had with scp and the
lack of /usr/local/bin in the destination hosts $PATH is overcome by
adding the following to sshd2_config --

subsystem-sftp /usr/local/bin/sftp-server

If that is why your scp fails, then changing that line seems much easier
than rebuilding with a different --prefix config.

maldata

0 new messages