Thanks guys. I did not realise that the router was doing this for me.
It makes sense now. Regards, Andy Fastream Technologies wrote: > Hello Andy, > > Addition to what Wilfried said, if your router is unable to parse the > contents of the PASV command response, (in cases like stupid router or SSL), > you need to define a manual pasv port range and forward up to 5-6k ports > from your router. These are the ports that the client will connect to when > transferring files or folder listings, in PASV mode. > > Best Regards, > > SZ > > > On 2/8/08, info2004 <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Allowing port 21 through my router when using TFTPClient caused a data >> error >> when attempting to send a file. >> >> Allowing port 20 cured this. >> >> Sniffing the net showed that 22 has worked in some cases. Also, there is a >> difference between active and passive in terms of the extra port used. >> >> Can TFTPClient just use the one port? I am sure that I normally only need >> to >> open port 21 at the router for things like CuteFTP. >> >> ...Andy >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be >> -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
