Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Username

Subject

Message body

Font colour:

Font size:

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

martin

2023-08-24

@xehpuk: I've documented that opening tunneled sessions is not possible from the Login dialog, if that's what you were missing:
https://winscp.net/eng/docs/ui_login#opening_in_putty
(Bug 2116 didn't change that. It was never possible).

xehpuk

2023-08-23 16:24

@martin It would be awesome if you documented the change from 2116. At least I couldn't find it.

martin

Re: Is it fixed?

2022-09-22

@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:
Issue 2115 – Allow opening tunneled session in PuTTY from Login dialog
Meanwhile, I'll disable opening tunneled sessions in PuTTY from the Login dialog:
Issue 2116 – Prevent opening tunneled sessions in PuTTY from Login dialog as it cannot work

scolom

Re: Is it fixed?

2022-09-20 11:50

@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

martin

Re: Is it fixed?

2022-09-08

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

scolom

Is it fixed?

2022-09-06 09:56

I'm still having this issue in 5.21.2v

martin

2010-03-31

Thanks. I'll check it.

Eugen

2010-03-29 13:02

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

Guest

Re: Tunnel and "Open in Putty"

2010-03-29 12:32

FAR manager 2.0.1420 x86
WinSCP Plug-in 1.6.2

martin

Re: Tunnel and "Open in Putty"

2010-03-29

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

Eugen

Tunnel and "Open in PuTTY"

2010-03-29 00:18

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