Spurious "Connection reset by peer" problems anybody?

[Ken Brown]

On 2/21/2011 9:26 AM, Corinna Vinschen wrote:
> On Feb 21 15:01, Corinna Vinschen wrote:
>> On Feb 21 08:49, Ken Brown wrote:
>>> On 2/21/2011 5:43 AM, Corinna Vinschen wrote:
>>>> Hi listies,
>>>>
>>>>
>>>> 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?
>>>>
>>>> If so, I might have a solution for this problem.  The code exists, but
>>>> personally I don't have any such problem, so I can't test if it helps,
>>>> and I'm reluctant to apply this to Cygwin without need.
>>>>
>>>> Therefore I need a guinea pig for this change.  Any takers?
>>>
>>> I have one situation in which I often get a "Software caused
>>> connection abort" message.  I'll be glad to test your change.
>>
>> I spoke too soon. [...]
>
> Er... btw., is the situation something which is local to your
> environment or is it something which can be easily reproduced?

The short answer is that it wouldn't be easy.  Here are the details:

I keep a local mirror of the emacs bzr repository.  I connect to the 
repository via bzr+ssh.  Every few days I refresh my mirror with 'bzr 
up'.  When I do this from work, where I have a fast ethernet connection, 
there's no problem.  When I do it from home, where I connect to the 
internet via a wireless router, it often fails with the "Software caused 
connection abort" message.  I keep retrying and eventually it works. 
Sometimes it takes 10 tries, other times it works on the first try.

I've had similar problems in the past when using rsync to maintain a 
local mirror of the texlive repository.  In that case I think the error 
message was always "Connection reset by peer".  Once again, the problem 
only occurred when working from home.

I've always assumed that there was some issue with my home network setup 
or my ISP, but I had no idea how to track it down.  It never occurred to 
me that it could be a Cygwin/Windows problem.

Ken

--
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