1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

big troubles with FTP and FlashFXP adressing :(

Discussion in 'Cisco/Linksys Wireless Routers' started by MsPa1nT, May 23, 2005.

  1. MsPa1nT

    MsPa1nT Network Guru Member

    So this is kind of a big problem...

    The thing is that i dont seem to get FTP working properly. The reason for me to set up a FTP server was that a pal would direct trafic from an FTP site to my server with his FlashFXP. He can connect to me and se the directory, but when he tries to upload soemthing, it works for maybe 2sec and then it terminates the connection to him so that he gets kicked out. I haven't any option enabled that says "block FXP connections" and from what i know i have opened the port 20-21 and the ports i have choosen to use for incoming connection.

    The thing is that we stoped trying so i started the server on my laptop and installed a client (leechftp) on my workstation. When i connect to the server with the local IP adress from my workstation i get a total loss of connections on every port it seems. MSN, Mozilla and everything else dies which is kind of weird. I also put up the exact same ports to the client computer (workstation) so that i can use active mode, but i have also tried passive mode and it's the same.

    I've put in the default Startup script which should help against the Torrent shutdown and i have also tried without it but it does not help anything..
     
  2. rdhw

    rdhw Network Guru Member

    If you are running an FTP Server on a client PC behind a NAT router, then you need to:

    a) in the FTP server configuration, identify a specific range of TCP ports which may be used by the FTP server to accept incoming passive-mode data connections (for example, 59000 to 59019 for twenty simultaneous connections);

    b) in the FTP Server configuration, you will need to inform it of the WAN IP address of your router (as allocated by your ISP), so that the server can rewrite some of the responses it issues to clients in the command stream (otherwise it will use its own LAN IP address, which is meaningless to remote FTP clients);

    c) in your router, configure port-forwards to the FTP Server PC for (i) TCP port 21 (or whatever port number you have configured for the FTP command stream), and (ii) the same range of TCP ports as configured in (a) above.

    If the remote FTP client is also behind its own NAT router, and if your FTP Server is listening on a non-standard port (other than 21), then there might be problems with the NAT router at the FTP client end: if so, these problems can be resolved by setting the remote FTP client into Passive Mode.
     

Share This Page