X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ferrors.but;h=59338ebc10a1eda594838379d874f8d3f2dcef44;hb=fdcdecace939ea7784ce539c0596d6432507e1c1;hp=51786b98c41b1ead712966f3ed2ed06aaf984c3f;hpb=8758cbf028777d17b80cc2f5b1058551768f99c6;p=PuTTY.git diff --git a/doc/errors.but b/doc/errors.but index 51786b98..59338ebc 100644 --- a/doc/errors.but +++ b/doc/errors.but @@ -1,4 +1,4 @@ -\versionid $Id: errors.but,v 1.4 2003/01/31 23:18:44 ben Exp $ +\versionid $Id: errors.but,v 1.8 2004/05/20 12:48:19 simon Exp $ \C{errors} Common error messages @@ -144,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} @@ -170,11 +188,11 @@ 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 @@ -185,10 +203,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 @@ -204,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. +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} @@ -242,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.