have you tried increasing your timeout?
Normally, you would not see the PASV command when not going through a
firewall but apparently the PORT command failed for some reason or
another so the protocol fell back on a passive transfer. Clearly
passive mode is supported by that server since it succeeded the first
time.
You're getting a net timeout on the passive data connection so maybe
it's your timeout and the server is a bit slow.
Can you read any FTP site through your firewall or do yo ujust have
problems with this one?
Sterling
> Two examples:
>
> There seems to be difference in following sections:
>
> 1) without firewall
>
> Net-log: "200 Type set to I."
> Net-log: [["PORT" port/locals/active-check] "200"]
> Net-log: [
> "PASV" "227"]
>
> 2) using firewall
>
> Net-log: "200 Type set to I."
> Net-log: [
> "PASV" "227"]
>
> I can't get it working, even after studying FAQ, How-Tos, etc. I also
> tried to set:
>
> system/schemes/FTP/proxy/host: 194.196.81.129
> ;system/schemes/FTP/proxy/port-id: 1080
> ;system/schemes/FTP/proxy/user: "user-name"
> ;system/schemes/FTP/proxy/pass: "password"
> ;system/schemes/FTP/proxy/type: 'socks4
>
> , where user-name and password are settings I use in Windows Commander
> FTP settings and it works with WC. I hope the solution is simple :-)
>
>
> Thanks,
>
> -pekr-
>
>
