X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/07ffa166c69e2c796d19c1b87d091beb89135ab9..eecca84d87d0b378a6a0af7f7651d0b9dc1514e9:/doc/errors.but

diff --git a/doc/errors.but b/doc/errors.but
index 6c0054d6..211e71f9 100644
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -1,4 +1,4 @@
-\versionid $Id: errors.but,v 1.3 2003/01/30 10:19:05 simon Exp $
+\versionid $Id: errors.but,v 1.7 2003/07/12 13:25:43 jacob Exp $
 
 \C{errors} Common error messages
 
@@ -73,6 +73,18 @@ have configured PuTTY to consider strong enough.
 
 See \k{config-ssh-encryption} for more information on this message.
 
+\H{errors-toomanyauth} \q{Server sent disconnect message type 2
+(SSH_DISCONNECT_PROTOCOL_ERROR): "Too many authentication failures for root"}
+
+This message is produced by an OpenSSH (or Sun SSH) server if it
+receives more failed authentication attempts than it is willing to
+tolerate.  This can easily happen if you are using Pageant and have a
+large number of keys loaded into it.  This can be worked around on the
+server by disabling public-key authentication or (for Sun SSH only) by
+increasing \c{MaxAuthTries} in \c{sshd_config}.  Neither of these is a
+really satisfactory solution, and we hope to provide a better one in a
+future version of PuTTY.
+
 \H{errors-memory} \q{Out of memory}
 
 This occurs when PuTTY tries to allocate more memory than the system
@@ -132,6 +144,24 @@ type of message, the first thing you should do is check your
 the server may have sent diagnostic messages explaining exactly what
 problem it had with your setup.
 
+\H{errors-access-denied} \q{Access denied}, \q{Authentication refused}
+
+Various forms of this error are printed in the PuTTY window, or
+written to the PuTTY Event Log (see \k{using-eventlog}) during
+authentication.
+
+If you see one of these messages, it means that the server has refused 
+all the forms of authentication PuTTY has tried and it has no further
+ideas.
+
+It may be worth checking the Event Log for diagnostic messages from
+the server giving more detail.
+
+This error can be caused by buggy SSH-1 servers that fail to cope with
+the various strategies we use for camouflaging passwords in transit.
+Upgrade your server, or use the workarounds described in
+\k{config-ssh-bug-ignore1} and possibly \k{config-ssh-bug-plainpw1}.
+
 \H{errors-crc} \q{Incorrect CRC received on packet} or \q{Incorrect
 MAC received on packet}
 
@@ -192,20 +222,15 @@ of \c{su} do it automatically.
 \H{errors-connaborted} \q{Network error: Software caused connection
 abort}
 
-In modern versions of PuTTY, you should not see this error.
-
-Windows's documentation about this error condition is not very good,
-but as far as we can tell, this error occurs when PuTTY is listening
-on a port, another program makes a connection to that port, but
-closes the connection so fast that PuTTY has no time to answer it.
+This error occurs when the Windows network code decides that your
+network connection is dead. For example, it will happen if you pull
+the network cable out of the back of an Ethernet-connected computer,
+or if Windows has any other similar reason to believe the entire
+network has become unreachable.
 
-PuTTY only ever listens on a port when it is doing local-to-remote
-port forwarding (see \k{using-port-forwarding}); and if an incoming
-connection on that port receives this error, PuTTY should simply
-close the connection and continue without error.
-
-If you see this error in PuTTY 0.53 or above, we would welcome a
-report of the circumstances.
+We are not aware of any reason why this error might occur that would
+represent a bug in PuTTY. The problem is between you, your Windows
+system, your network and the remote system.
 
 \H{errors-connreset} \q{Network error: Connection reset by peer}
 
@@ -230,3 +255,14 @@ access.
 Check that you are connecting with the correct protocol (SSH, Telnet
 or Rlogin), and check that the port number is correct. If that
 fails, consult the administrator of your server.
+
+\H{errors-conntimedout} \q{Network error: Connection timed out}
+
+This error means that the network connection PuTTY tried to make to
+your server received no response at all from the server. Usually
+this happens because the server machine is completely isolated from
+the network, or because it is turned off.
+
+Check that you have correctly entered the host name or IP address of
+your server machine. If that fails, consult the administrator of
+your server.