Host has not answered for 15 seconds

Hi,

I'm using the synchronization feature of WinSCP on some Windows XP laptops which connect to a Windows XP WinSCP box. The synchronization feature is run via a script which I keep the logs.

Some users have the following in there log file:

Host has not answered for 15 seconds.
Wait for another 15 seconds? Pressing 'Abort' button will close session.
(A)bort, (R)etry: Abort

Why does this happen? How can I prevent it from happening?

Thanks.

Have you tried setting longer timeout?

How can I automatically define the answer as abort? The problem for me is that I am running a script early in the morning without any user intervention, and the retry or abort questions is making the console to stay open.

aadami wrote:

How can I automatically define the answer as abort? The problem for me is that I am running a script early in the morning without any user intervention, and the retry or abort questions is making the console to stay open.

Have you tried "option batch abort"?

Would you mind telling me how to change timeout with WinSCP script? I've tryed "option batch off" - script doesn't respond even when external command had finished it's tasks (until I press "R").
"option batch retry" - unkown option..
"option timeout 1000" - unkown option..
How to avoid this message:?:

Piotrek wrote:

Would you mind telling me how to change timeout with WinSCP script? I've tryed "option batch off" - script doesn't respond even when external command had finished it's tasks (until I press "R").
"option batch retry" - unkown option..
"option timeout 1000" - unkown option..
How to avoid this message:?:

This FAQ will give you hopefully some idea how to do that.

martin wrote:

This FAQ will give you hopefully some idea how to do that.

Martin,
This feature has caused me great agony and wasted minutes. Of course having your program in the first place has caused me great convenience and saved lots of time, but I think there is a basic mistake here that causes people a lot of pain.

Why not just automatically retry by default? Why not reconnect by default? It is the internet after all. Many people have unreliable networks, and a longer timeout isn't going to help. I waste so much time because what I told the program to do, it didn't do when I get back to the computer. I may get this error 20 or 30 times in a single batch. I spend my life clicking "Retry". I am trying to decide whether to go back to Cygwin command line, because using regular SCP -R just never has exhibited this problem.

Thanks,
James

jamescarpino wrote:

Why not just automatically retry by default? Why not reconnect by default?

It will be solved in the next version.