Post a reply

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)


Topic review


Theres no email address in your profile

As mentioned previously, you need to register and login to see it.

Thank you

WinSCP Version 5.5.0 (Build 3839) (OS 6.1.7601 Service Pack 1 - Windows Server 2008 R2 Enterprise)

No SSL , no TLS

Theres no email address in your profile

Re: Port configuration and session timeout problems

What version of WinSCP are you using?
Are you using SSL/TLS?
What is your FTP server?

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file command-line argument. 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.

Port configuration and session timeout problems

An automated winscp script has been working between two servers in both directions for 6 months.

From last week, at a random file(both directions), session is interrupted. I tried a 'timeout' but it results in a recursive error, i mean, first time the script reconnect, the forth or fifth file again stops the session, after that, the first or second file do it and finally the app is not capable to start session, sometimes it becomes an infinite loop, sometimes it results in Winscp-APPCRASH.

There have been some kind of port configuration somewhere because from last week, the only way to avoid a
'Can't open data connection' error is setting the task as 'active' although it was working as 'passive' for 6 months, but the main problem with connection continue.