>Hello,
>I finally got around to try this last night. I got it to work except for one thing. When someone ftp's into my windows box threw the linux gateway they cant do an ls command. They don't see whats in the directory. Do you know how to fix this?
>Thanks
> --MIke
>
>++++First Reply++++
>Mike,
>
>This can be accomplished using ipmasqadm with port forwarding enabled in your kernel. If both are installed, then you can use the following examples.
>
>I'm going to use a public ip address of 209.19.19.2 as an example. Just fill in the public ip address of your linux box in it's place when you do this on your network.
>
>example 1 (with no ftp daemon running on gateway box)
>
>ipmasqadm portfw -a -P tcp -L 209.19.19.2 21 -R 192.168.1.2 21
>
>example 2 (ftp daemon also running on gateway box, so we redirect port 4040 to the ftp services on the winbox
>
>ipmasqadm portfw -a -P tcp -L 209.19.19.2 4040 -R 192.168.1.2 21

Jason's post has some excellent suggestions, but one other thing to ask is this.

Is the client using active or passive ftp? Make sure the client connects with passive ftp. A client using active ftp will try communicating on more ports than the original connect port. When it tries to do this, then it can't complete the command tried because it can't make a connection on the port it's trying to connect to.

I have seen this specific behaviour when trying to use active ftp on a server that will only let you use passive ftp.

regards,

JE