Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	Jeff Mincy <jeff AT delphioutpost DOT com>
MIME-Version:	1.0
Message-ID:	<15416.47547.430000.951840@antarres.muniversal.com>
Date:	Sun, 6 Jan 2002 15:55:23 -0500
To:	Adrian Phillips <adrianp AT powertech DOT no>
Cc:	"James Hall" <james DOT c DOT hall AT ntlworld DOT com>, <cygwin AT cygwin DOT com>
Subject:	Re: Newbie ssh question
In-Reply-To:	<87sn9j3hv1.fsf@grannyogg.localnet>
References:	<87sn9j3hv1 DOT fsf AT grannyogg DOT localnet>
X-Mailer:	VM 7.00 under 21.4 (patch 6) "Common Lisp (Windows)" XEmacs Lucid

   From: Adrian Phillips <adrianp AT powertech DOT no>
   Date: 06 Jan 2002 11:15:46 +0100
   
   >>>>> "James" == James Hall <james DOT c DOT hall AT ntlworld DOT com> writes:
   
       James> I've recently installed Cygwin and XFree86 on my W2K
       James> machine, and am highly pleased with it.
   
       James> Main use is to run stuff on my machine at work, and saves
       James> constantly re-booting between Windows and Linux on my home
       James> machine.
   
       James> I consequently make much use of ssh and X forwarding. All
       James> works excellently, but for one problem. Any remote Xterm,
       James> unless used pretty constantly, falls over with the message
   
       James> 	"Read from remote host x.x.x.x: Connection reset by peer
       James> Connection to x.x.x.x closed."
   
   Do you have a firewall in between. Firewalls throw away connections
   when there unused for a while,
   
For example, Sonicwalls have Network Connection Inactivity Timeout

   Try turning on KeepALive (or whatever the option is called now),
   
Also, there is how hard windows tries to keep connections alive.

This is in the PuttyFAQ
 
 The timeout value can't be set on per application or per session
 basis. To increase the TCP timeout globally, you need to add the
 following key to the registry
 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxDataRetries
 in Win95/98/ME (it must be DWORD in Win95, or String in Win98/ME),

 Then set the key's value to something like 10. This will cause
 Windows to try harder to keep connections alive instead of
 abandoning them.

P.S. Have fun doing regedit.  
P.P.S, do be careful.  This would be a good time to backup your machine.

   Your mouse has moved.
   Windows NT must be restarted for the change to take effect.
   Reboot now?  [OK]

Snirk.

-jeff


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -