Did-not-respond vs time-out issue

Advertisement

miking
Guest

Did-not-respond vs time-out issue

I'm trying to connect to a particularly-slow FTP server.
- Initially I got "Timeout detected. Connection failed." messages after 15seconds.
- I changed the "Server Response Timeout" from 15sec to 60sec...
- ...and now (after 21sec) I get "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Connection failed."

I've tried a few other FTP clients - some give similar results to WinSCP but others successfully connect after about a minute.

Any suggestions?

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
40,476
Location:
Prague, Czechia

Re: Did-not-respond vs time-out issue

Please attach a full log file showing the problem (using the latest version of WinSCP). Please also post a log from client that can connect.

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. 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.

Reply with quote

miking
Guest

Re: Did-not-respond vs time-out issue

Hi prikryl,
Thanks for your response. Fortunately my provider was able to resolve the issue causing very slow server response times. Unfortunately however this makes it impossible for me to troubleshoot and get to the bottom of the winscp timeout issue now.
Regards, Michael

Reply with quote

Advertisement

You can post new topics in this forum