Looks suspiciously like firewall or router interference (which can be application-specific...). Note that if Pro is set to use one mode (Passive, say), and that hits issues it may try a failback to the other mode (which may simply not work at all - but it's worth a try in case mode-1 was the 'wrong' one).
If you want to generate & forward a Support Zip with debug-out to our (new) ticket system, we can take a look. There's a Contact Support link in that article.
But it may be we can only guess at the cause: in your first example the FTP server is actively refusing a connection, and in the second, there's a timeout (or, the server is actually sending a response and Pro doesn't hear it because something is interfering with or blocking it)
BTW, you masked the server IP in the 2nd example, but left the IP in the first example 'in clear'![;)]( "Wink")
If you want to generate & forward a Support Zip with debug-out to our (new) ticket system, we can take a look. There's a Contact Support link in that article.
But it may be we can only guess at the cause: in your first example the FTP server is actively refusing a connection, and in the second, there's a timeout (or, the server is actually sending a response and Pro doesn't hear it because something is interfering with or blocking it)
BTW, you masked the server IP in the 2nd example, but left the IP in the first example 'in clear'
