X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Date: Wed, 13 Oct 2010 22:09:48 +0000 From: jurriaan AT rivierenland DOT xs4all DOT nl To: cygwin AT cygwin DOT com Subject: Re: scp fails without a warning. Message-ID: <20101013220948.GA7669@onderneming10.xs4all.nl> References: <45833C44DA56B948A31517B07F7CCEC112B45EDB4D AT VAFF06-MABPRD01 DOT ad DOT gd-ais DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45833C44DA56B948A31517B07F7CCEC112B45EDB4D@VAFF06-MABPRD01.ad.gd-ais.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 AT 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 AT 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 http://www.openssh.com/faq.html 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, Jurriaan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple