nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-10 01:48:00 +00:00
Code Issues Projects Releases Wiki Activity

In the entry about twiddling Windows TCP timeouts, mention that it's OK to

Browse Source 
create the registry values, and link back to the original MS KB articles.

[originally from svn r4259]
This commit is contained in:
Jacob Nevins 2004-05-26 09:19:48 +00:00
parent 847f86892d
commit b8e4b6f9b9
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/faq.but
View File

@ -1,4 +1,4 @@
\versionid $Id: faq.but,v 1.70 2004/05/22 11:09:31 simon Exp $
\versionid $Id: faq.but,v 1.71 2004/05/26 09:19:48 jacob Exp $
\A{faq} PuTTY FAQ
@ -673,12 +673,16 @@ This is a Windows problem, not a PuTTY problem. The timeout value
can't be set on per application or per session basis. To increase
the TCP timeout globally, you need to tinker with the Registry.
On Windows 95, 98 or ME, the registry key you need to change is
On Windows 95, 98 or ME, the registry key you need to create or
change is
\c HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\
\c MSTCP\MaxDataRetries
(it must be of type DWORD in Win95, or String in Win98/ME).
(See MS Knowledge Base article
\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;158474}{158474}
for more information.)
On Windows NT or 2000, the registry key is
@ -686,6 +690,9 @@ On Windows NT or 2000, the registry key is
\c Parameters\TcpMaxDataRetransmissions
and it must be of type DWORD.
(See MS Knowledge Base article
\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;120642}{120642}
for more information.)
Set the key's value to something like 10. This will cause Windows to
try harder to keep connections alive instead of abandoning them.