X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/91f80e36254e90f476cf5bcce0ef02af62ec9534..4fe91af386b4a0561478340cdf5d18672f7f5b55:/doc/errors.but diff --git a/doc/errors.but b/doc/errors.but index 0c3e211a..4b9496df 100644 --- a/doc/errors.but +++ b/doc/errors.but @@ -1,4 +1,4 @@ -\versionid $Id: errors.but,v 1.1 2002/10/01 16:27:36 simon Exp $ +\versionid $Id: errors.but,v 1.9 2004/07/22 12:38:37 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 @@ -93,7 +105,7 @@ memory} error. This can happen in SSH 2, if PuTTY and the server have not enabled encryption in the same way (see \k{faq-outofmem} in the FAQ). Some -versions of OpenSSH have a knownq problem with this: see +versions of OpenSSH have a known problem with this: see \k{faq-openssh-bad-openssl}. This can also happen in PSCP or PSFTP, if your login scripts on the @@ -113,6 +125,28 @@ Similarly, any error message starting with \q{Assertion failed} is a bug in PuTTY. Please report it to us, and include the exact text from the error message box. +\H{errors-key-wrong-format} \q{Unable to use this private key file}, +\q{Couldn't load private key}, \q{Key is of wrong type} + +Various forms of this error are printed in the PuTTY window, or +written to the PuTTY Event Log (see \k{using-eventlog}) when trying +public-key authentication, or given by Pageant when trying to load a +private key. + +If you see one of these messages, it often indicates that you've tried +to load a key of an inappropriate type into PuTTY, Plink, PSCP, PSFTP, +or Pageant. + +You may have specified a key that's inappropriate for the connection +you're making. The SSH-1 and SSH-2 protocols require different private +key formats, and a SSH-1 key can't be used for a SSH-2 connection (or +vice versa). + +Alternatively, you may have tried to load an SSH-2 key in a \q{foreign} +format (OpenSSH or \cw{ssh.com}) directly into one of the PuTTY tools, +in which case you need to import it into PuTTY's native format +(\c{*.PPK}) using PuTTYgen - see \k{puttygen-conversions}. + \H{errors-refused} \q{Server refused our public key} or \q{Key refused} @@ -132,6 +166,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} @@ -151,14 +203,18 @@ gone wrong in the encryption or decryption process. It's difficult to tell from this error message whether the problem is in the client or in the server. -A known server problem which can cause this error is described in -\k{faq-openssh-bad-openssl} in the FAQ. +If you get this error, one thing you could try would be to fiddle +with the setting of \q{Miscomputes SSH2 encryption keys} on the Bugs +panel (see \k{config-ssh-bug-derivekey2}). + +Another known server problem which can cause this error is described +in \k{faq-openssh-bad-openssl} in the FAQ. -\H{errors-x11-proxy} \q{Authentication failed at PuTTY X11 proxy} +\H{errors-x11-proxy} \q{PuTTY X11 proxy: \e{various errors}} -This error is reported when PuTTY is doing X forwarding. It is sent -back to the X application running on the SSH server, which will -usually report the error to the user. +This family of errors are reported when PuTTY is doing X forwarding. +They are sent back to the X application running on the SSH server, +which will usually report the error to the user. When PuTTY enables X forwarding (see \k{using-x-forwarding}) it creates a virtual X display running on the SSH server. This display @@ -169,10 +225,10 @@ details it needs to enable clients to connect, and the server should put this mechanism in place automatically, so your X applications should just work. -A common reason why people see this message is because they used SSH -to log in as one user (let's say \q{fred}), and then used the Unix -\c{su} command to become another user (typically \q{root}). The -original user, \q{fred}, has access to the X authentication data +A common reason why people see one of these messages is because they +used SSH to log in as one user (let's say \q{fred}), and then used +the Unix \c{su} command to become another user (typically \q{root}). +The original user, \q{fred}, has access to the X authentication data provided by the SSH server, and can run X applications which are forwarded over the SSH connection. However, the second user (\q{root}) does not automatically have the authentication data @@ -188,20 +244,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. +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. -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. - -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} @@ -226,3 +277,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.