@scolom: Ok, that's not what the post was about. But ok, I see. It's because the tunnel is not opened. But now that PuTTY supports tunneling natively, WinSCP tunnel settings can be translated to PuTTY.
I've added this request to the tracker, you can vote for it there:
Bug 2115 – Allow opening tunneled session in PuTTY from Login dialog
Meanwhile, I'll disable opening tunneled sessions in PuTTY from the Login dialog:
Bug 2116 – Prevent opening tunneled sessions in PuTTY from Login dialog as it cannot work

@martin: Thanks for your answer.
I'm referring to the original one. When having a tunnel (jump host) the 'Open in PuTTY' option in the right click site options doesn't use the tunnel.

Notice that using the 'Open session in PuTTY' once connected using the GUI works.

Thanks

@scolom: There are two distinct issues discussed in this topic. Which one are you referring to?

I'm still having this issue in 5.21.2v

Thanks. I'll check it.

Hm.. there seems to be another bug (?):
If IPv4 is forced (Connection tab), it seems to have no effect on tunnel connection.

Configuration:
My local server is listening on 0.0.0.0 (all IPv4 interfaces?).
If I give localhost as tunnel host, the tunnel connection can not be established (Network error: Connection refused.), but if I give 127.0.0.1 then it works fine.

Using:
FAR 2.0.1420 x86
WinSCP 1.6.2
Windows 7 (uses IPv6 for local connections by default)

Greats
Eugen

FAR manager 2.0.1420 x86
WinSCP Plug-in 1.6.2

What version of the plugin are you using? I believe this has been fixed already.

Hey,

First thanks for the great Plug-in!

Found a bug, but I don't really know, if its a bug of plug-in or WinSCP code.

If you set up a session using a tunneled connection, connect to a host that is not directly reachable from your network and then select "Open in PuTTY", PuTTY will try to connect directly and of course fail...

Why not simply pass local host and local port of the tunnel created by the plug-in to PuTTY if connected trough tunnel?

Greats
Eugen