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
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
Hello Andy,
If you are behind a router then you have to switch to passive mode. This
means that the FTP server will listen on another port for the data
transfer and the client will then connect to that port. In normal mode
the client will listen on another port but blocked by the router.
---
Rgds
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 T
