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.

Options
Add an Attachment

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

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

Options

Topic review

rick`

I have e-mailed you the log.
martin

Re: Host has not answered for more than x seconds. Still Waiting

Please post a full log file showing the problem.

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. For posting extensive logs you may use pastebin or similar application. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
rick`

Host has not answered for more than x seconds. Still Waiting

Version: 4.17 (Build: 413) on Windows XP SP2

I use the GUI Commander interface, and run SFTP protocol v5, Keepalives 5s interval dummy commands, no compression, SSH protocol v2, Blowfish cipher.

Problem: Experiencing "How has not answered for more than x seconds. Still waiting..." - On DOWNLOADS ONLY.

Randomly started having this problem. Uploads to the same remote location are not affected at all, however I have to stay where I am so I can click 'Abort' then 'Reconnect' every x seconds whenever I get a timeout so I can keep downloading a file. File size is irrelevant, I have regularly download and/or uploaded files between 1kb and over 2gb. All of them have suffered from this 'timout' problem and I have no idea what is causing it.

Server settings haven't been changed, local settings haven't been changed. It just stopped .. working, I guess.