X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ferrors.but;h=bf9672d05a0c7d28a268aef0565dc1cba08c6e55;hb=91653a10c6e6b9d57688e1d7dd7403625ea670a0;hp=2d253520feb86affc24f32bad96d19fbf9ce04f8;hpb=4d8782e74fed043fdf549718f99494622fe9e79b;p=PuTTY.git

diff --git a/doc/errors.but b/doc/errors.but
index 2d253520..bf9672d0 100644
--- a/doc/errors.but
+++ b/doc/errors.but
@@ -338,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.