Para redirigir un puerto remoto a uno local , donde por ejemplo corra un servidor telnet
putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession
plink mysession -R 5023:mytelnetserver.myhouse.org:23
para especificar una dirección IP para escuchar al final de el tunel: DUDA
(To specify an IP address for the listening end of the tunnel, prepend it to
the argument:)
plink -L 127.0.0.5:110:localhost:110 myhost
Directamente de la ayuda del putty:
"To forward a local port (say 5110) to a remote destination (say
popserver.example.com port 110), you can write something like one of these:
putty -L 5110:popserver.example.com:110 -load mysession
plink mysession -L 5110:popserver.example.com:110
To forward a remote port to a local destination, just use the -R option instead
of -L:
putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession
plink mysession -R 5023:mytelnetserver.myhouse.org:23
To specify an IP address for the listening end of the tunnel, prepend it to the
argument:
plink -L 127.0.0.5:23:localhost:23 myhost
To set up SOCKS-based dynamic port forwarding on a local port, use the -D option.
For this one you only have to pass the port number:
putty -D 4096 -load mysession
For general information on port forwarding, see section 3.5.
These options are not available in the file transfer tools PSCP and PSFTP."
* Bug en WXP SP2: "Some people who ask PuTTY to
listen on localhost addresses other than 127.0.0.1 to forward services such as
SMB and Windows Terminal Services have found that doing so no longer works since
they upgraded to WinXP SP2.
This is apparently an issue with SP2 that is acknowledged by Microsoft in MS
Knowledge Base article 884020. The article links to a fix you can download.
(However, we've been told that SP2 also fixes the bug that means you need to use
non-127.0.0.1 addresses to forward Terminal Services in the first place.)"