martin wrote:

Thanks. Though this is not a verbose FileZilla log.

Did you try the latest version of WinSCP?

Also try to turn off Reuse TLS/SSL session ID for data connections:
https://winscp.net/eng/docs/ui_login_tls

I did and it seems to be working now
Thank you

Thanks. Though this is not a verbose FileZilla log.

Did you try the latest version of WinSCP?

Also try to turn off Reuse TLS/SSL session ID for data connections:
https://winscp.net/eng/docs/ui_login_tls

Anonymous wrote:

this is with verbose turned on

Thank you

this is with verbose turned on

Thank you

Please attach a verbose FileZilla log file.

We were using WinSCP to connect to another server for 6-8 months. Several months ago someone wrote a script an it too worked. About 1 month ago the script failed, I figured it was a password so I attempted to log in using the gui. It too failed. I was able to log in using filezilla and have been using it since, the problem is I or someone has to manually log in and execute this process, the script made it so much easier.

We make the connection and I get a 425. I looked the error up and it says it could be a windows firewall problem. My problem with this explanation is all parms on filezilla and WinSCP match

I did some reading and saw passive maybe a problem, so I checked and we are using passive mode. At this point I'm throwing myself on the mercy of the forum for help.
We are at build 5.1.2 (build 2816( but you will see all that with the log I am loading.

Thank you in advance
Mace