consistency wrote:

i have a similar "problem" with ssh connections (for all my 4.x winscp versions). if i connect to an ip in my lan where no ssh server is running, winscp runs in a timeout without leaving me an option to cancel the try of winscp to connect.

here i connect to an local network ip where no ssh server is installed:

also if i know that winscp can't connect because i have to start/install ssh server first i have to wait (in my case 22sec) for winscp to show me the following error window:
<invalid link removed>
and then i only have 5sec to press ok, if a miss to press the ok button i have to wait another 22sec in the "freeze mode" until the error window reappears and i can press ok.

it would be great to let winscp try to connect in backgroud but leaving me the option to cancel the connection try.

This issue has been added to the tracker:
https://winscp.net/tracker/757

i have a similar "problem" with ssh connections (for all my 4.x winscp versions). if i connect to an ip in my lan where no ssh server is running, winscp runs in a timeout without leaving me an option to cancel the try of winscp to connect.

here i connect to an local network ip where no ssh server is installed:
<invalid link removed>
also if i know that winscp can't connect because i have to start/install ssh server first i have to wait (in my case 22sec) for winscp to show me the following error window:
<invalid link removed>
and then i only have 5sec to press ok, if a miss to press the ok button i have to wait another 22sec in the "freeze mode" until the error window reappears and i can press ok.

it would be great to let winscp try to connect in backgroud but leaving me the option to cancel the connection try.

kag wrote:

I'm having the same problem and I'm running 4.3.3 build 1340 on Windows XP SP3.

I have sent you an email.

I'm having the same problem and I'm running 4.3.3 build 1340 on Windows XP SP3.

neijygof wrote:

I am having the same problem... may I send you an e-mail requesting the debug version?

Sure. But first, pleae make sure you are using the latest version of WinSCP.

I am having the same problem... may I send you an e-mail requesting the debug version?

Thank you in advance,

neijygof

I'm sending you my email for a debug version as well due to having this issue. It simply freezes seemingly at random. I'll go to do some editing on a file for about 10 minutes, and when I come back to the WinSCP window to upload it, it is frozen (Not Responding) and has to be killed and reopened.

-elraver

I sent an email too, since I've been getting the same errors and problems.

I have sent you mail

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

sorry, I forgot
WinSCP version: 4.3.2
(before this version, I was using ver 4.2.9 and I didnt noticed this bug, but I am not sure)
Windows Vista SP2

I use winscp mainly for FTP sites. And this error occoures very often, when winscp is connected and idle for some time. First, it gives me error like timeout and then I get this error:
Error getting name of current remote directory

I click OK and then winscp tries to reconnect (probably) - I can see only small blank window and whole program is frozen. Only way to close it is to kill winscp.exe via taskmanager or similar program.
I use FTP protocol with passive mode and this happens not only on one server.
Am I doing something wrong?