But both ends must support this mode.īecause even that can be problematic, since (a.) most end-users don't know much about FTP or computers in general and (b.) many FTP client and server products don't even support "passive mode" in 2015. This is so-called "passive mode FTP" and you turn that on in your client either with a command-line switch or a command entered once you have connected the command channel and logged on. Now, if both your FTP client and the remote FTP support a hack that was added in the 1980s to get around this limitation one way to get around this is to activate it for your FTP session. This means an FTP "client" must also be a "server." This "back channel" gets blocked by network devices pretty routinely. The problem is that it normally requires a connection back to you for the seprate channel (TCP connection) that it uses for data transfer. One of the things about FTP is that it is hostile to firewalls and NAT routers.
I missed seeing that when I replied to your PM regarding WebDAV as an alternative. everything seems to be working until I hit the mput command, which results in "200 PORT command successful", quickly followed by "425 Could not open data connection to port 59501: No route to host".Ahh.
0 kommentar(er)
