From: MS <jmstanfield@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Spurious "Connection reset by peer" problems anybody?
Date: Tue, 22 Mar 2011 23:27:00 -0000 [thread overview]
Message-ID: <4D89245A.6000503@gmail.com> (raw)
On Mon, 21 Feb 2011 11:43:52 Corinna Vinschen wrote:
>
> over the weekend I came across a description of a Windows socket problem
> which might affect some of us. Fortunately I also came across the
> potential solution.
>
> My question is, does anybody have a scenario in which he or she
> encounters weird "Connection reset by peer" or "Software caused
> connection abort" messages in Cygwin, possibly at the end of a
> connection attempt?
Only just joined the list specifically to reply about this.
On Windows 7 running rsync over ssh to a UNIX server I am repeatedly
getting the "connection reset by peer" error, causing rsync to fail. The
error occurs regularly but at inconsistent intervals. In an attempt to
get around it I wrote a rsync retry script, but even setting the number
of retries the script makes for each of the half-dozen rsync commands to
10 does not guarantee success. I was beginning to look for another Win 7
rsync/ssh solution when I decided to check the mailing list archives.
Has there been progress with this over the last few weeks? Rsycing to
the same UNIX server from my Linux machine is always fine though that
enjoys significantly faster bandwidth than the Win 7 PC (although that
has a decent ADSL connection, note that the Win 7 PC is not using wireless).
Is there anything I can try to resolve this as a working
cygwin/rsync/ssh solution looks like my ideal scenario. Cygwin newbie,
but technically proficient software engineer.
Thanks,
..matthew
--
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
next reply other threads:[~2011-03-22 22:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 23:27 MS [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 16:14 lynn
2011-02-21 10:44 Corinna Vinschen
2011-02-21 13:49 ` Ken Brown
2011-02-21 14:02 ` Corinna Vinschen
2011-02-21 14:26 ` Corinna Vinschen
2011-02-21 14:54 ` Ken Brown
2011-02-21 15:06 ` Corinna Vinschen
2011-02-21 15:27 ` Ken Brown
2011-02-21 15:34 ` Corinna Vinschen
2011-02-21 22:08 ` Ken Brown
2011-02-22 8:55 ` Corinna Vinschen
[not found] ` <AANLkTimoBKaVBj9yOvLJunrtEV0tY+ruJG2bHV7moc9q@mail.gmail.com>
2011-02-22 15:40 ` Mirko Vukovic
2011-02-22 15:55 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D89245A.6000503@gmail.com \
--to=jmstanfield@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).