This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: scp fails without a warning.

From: Wiles, Dale L. (NE) <>
Date: Wed, Oct 13, 2010 at 11:44:26AM -0400
> I updated cygwin yesterday (10/12/10) and rebooted my Windows XP (SP3) box.  Now, when I use scp from a Red Hat 5.5 box to my Windows box, scp quietly fails.
> If I run (from Red Hat) "scp uname@windowsbox:file .", I'm prompted for my password.  I type it in and then, a moment later, scp exits.  No data gets transferred and there is no error messages.  If I type in a garbage file name, I get the same results.  There is no error message.
> If I run "sftp uname@windowsbox:file ." I'm prompted for my password and the file transfers normally.  Unfortunately I need a recursive copy.
> I can also ssh into my windows box with no problem.
> /var/log/sshd.log exists, but is empty.
I had something like this (ssh OK, scp fails silently) a few years ago, 
and it was related to this:

The OpenSSH FAQ has something to that affect in section 2.9
2.9 - sftp/scp fails at connection, but ssh is OK.

sftp and/or scp may fail at connection time if you have shell
initialization (.profile, .bashrc, .cshrc, etc) which produces output
for non-interactive sessions. This output confuses the sftp/scp client.
You can verify if your shell is doing this by executing:

ssh yourhost /usr/bin/true

If the above command produces any output, then you need to modify your
shell initialization.

which I found on google using 'scp fails silently .bashrc' - there's
lots more info there.

Hope this helps,

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]