X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ferrors.but;h=bf9672d05a0c7d28a268aef0565dc1cba08c6e55;hb=91653a10c6e6b9d57688e1d7dd7403625ea670a0;hp=06c247c01e4c465ac35c2f4659b0af9aa5fa5546;hpb=12b6a4e7ddb5baef3f631ee35be15b89536e2160;p=PuTTY.git diff --git a/doc/errors.but b/doc/errors.but index 06c247c0..bf9672d0 100644 --- a/doc/errors.but +++ b/doc/errors.but @@ -1,5 +1,3 @@ -\define{versioniderrors} \versionid $Id$ - \C{errors} Common \i{error messages} This chapter lists a number of common error messages which PuTTY and @@ -58,20 +56,6 @@ in the same way as you would if it was new. See \k{gs-hostkey} for more information on host keys. -\H{errors-portfwd-space} \q{Out of space for port forwardings} - -PuTTY has a fixed-size buffer which it uses to store the details of -all \i{port forwardings} you have set up in an SSH session. If you -specify too many port forwardings on the PuTTY or Plink command line -and this buffer becomes full, you will see this error message. - -We need to fix this (fixed-size buffers are almost always a mistake) -but we haven't got round to it. If you actually have trouble with -this, let us know and we'll move it up our priority list. - -If you're running into this limit, you may want to consider using -dynamic port forwarding instead; see \k{using-port-forwarding}. - \H{errors-cipher-warning} \q{The first cipher supported by the server is ... below the configured warning threshold} @@ -354,3 +338,13 @@ things into PuTTY while the network is down, but it can also occur if PuTTY decides of its own accord to send data: due to a repeat key exchange in SSH-2 (see \k{config-ssh-kex-rekey}) or due to keepalives (\k{config-keepalive}). + +\H{errors-cannotassignaddress} \q{Network error: Cannot assign requested +address} + +This means that the operating system rejected the parameters of the +network connection PuTTY tried to make, usually without actually +trying to connect to anything, because they were simply invalid. + +A common way to provoke this error is to accidentally try to connect +to port 0, which is not a valid port number.