From 83372d79842f9a9c3debfb7a88456d24bfa34354 Mon Sep 17 00:00:00 2001 From: jacob Date: Tue, 15 Feb 2005 12:35:59 +0000 Subject: [PATCH] Extra note on "connection reset by peer" on Windows. Note default circumstances of cipher warning. (I haven't bothered with the similar kex warning since it doesn't come up in the default configuration, and is in any case unlikely to be common.) git-svn-id: svn://svn.tartarus.org/sgt/putty@5302 cda61777-01e9-0310-a592-d414129be87e --- doc/errors.but | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/errors.but b/doc/errors.but index 64409eae..722f24b7 100644 --- a/doc/errors.but +++ b/doc/errors.but @@ -69,7 +69,8 @@ this, let us know and we'll move it up our priority list. ... below the configured warning threshold} This occurs when the SSH server does not offer any ciphers which you -have configured PuTTY to consider strong enough. +have configured PuTTY to consider strong enough. By default, PuTTY +puts up this warning only for single-DES encryption. See \k{config-ssh-encryption} for more information on this message. @@ -272,6 +273,10 @@ connection out. See \k{faq-idleout} in the FAQ for more details. You may be able to improve the situation by using keepalives; see \k{config-keepalive} for details on this. +Note that Windows can produce this error in some circumstances without +seeing a connection reset from the server, for instance if the +connection to the network is lost. + \H{errors-connrefused} \q{Network error: Connection refused} This error means that the network connection PuTTY tried to make to -- 2.11.0