If you are connecting via FTP then Transmit uses between 3-5 different ports per ftp event (upload, download, permission change, etc). In a decent-length session this is a lot of ports and if you have any of those blocked by your firewall you'll get "Connection cannot be established" errors.
Assuming your firewall exists for a reason and your service does not support port22 connections you'll need a try a new FTP client.
I guess Transmit is using these "random" port assignments to validate (and consequently secure) non-SFPT traffic which is all very worthy. My beef is that in order to reduce the total traffic and hence the total number of ports used per session Transmit includes an improperly implemented local caching regime which has "broken" the whole application and is reason enough to look for something better.
Sad to say, but this dog might just have had his day.
Existing users, log in. New users, create a free account. Lost password?
Quality is declining... - julianps_dotmac
mourogers, are you using FTP, or SFTP?If you are connecting via FTP then Transmit uses between 3-5 different ports per ftp event (upload, download, permission change, etc). In a decent-length session this is a lot of ports and if you have any of those blocked by your firewall you'll get "Connection cannot be established" errors.
Assuming your firewall exists for a reason and your service does not support port22 connections you'll need a try a new FTP client.
I guess Transmit is using these "random" port assignments to validate (and consequently secure) non-SFPT traffic which is all very worthy. My beef is that in order to reduce the total traffic and hence the total number of ports used per session Transmit includes an improperly implemented local caching regime which has "broken" the whole application and is reason enough to look for something better.
Sad to say, but this dog might just have had his day.
Reply to This
Friday, December 07 2007 @ 12:34 AM PST