@YK-Tan: So glad you didnt delete the post, thank you sm for the help!

@super_edu2000: Unless you have version- or binary-specific rule in your firewall that would allow the old version but not the new one, it's more likely a coincidence than a problem related to the upgrade. If you believe otherwise, please post logs from both the old and the new version.

Hi this happened after I updated to the newest version 6.1.2. any idea what changed to now cannot be possible to access the server using the exact same config, port, login, evertyhing the same

Thanks for your feedback. Keep the post. I'm sure there will be others who make the same mistake and they might find it useful.

Thank you for the reply. It turns out that the cause of the problem is that the FTP server was simply not configured for the host server that I was using for testing purposes. I was able to connect to several other servers (on Linux) successfully today.

I'm sorry for wasting your time. Should I delete this post?

Double check if your local firewall is not blocking the connection. Can you post equivalent Robo-FTP log from the same local machine, showing how it successfully connects at the same time WinSCP cannot connect with the same settings?

Hello, I'm new to WinSCP, so if there is any form of detail that I should have mentioned, please do point it out!

WinSCP version: 5.21.3
Windows version: Windows 10 Pro

Previously, my company was using Robo-FTP services for file transfer purposes, until the company decided to find a replacement. Through some degree of research, I suggested to use WinSCP instead. However, as I was attempting to login a specific server session with the exact same credentials used on Robo-FTP, I received an error message which stated "Timeout Detected. (control connection)". I've tried changing the advanced settings here and there, but to no avail. The connection is in passive mode.

I have recorded the entire process within the attached log file below. Rather than a simple solution. I'd like to have some advice on what to pay attention to when facing this error. Could it be that it has something to do with the server host? Thank you in advance.