1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Setting up an FTP server... Not working....

Discussion in 'Networking (Hardware & Software)' started by Bikeman, 2008/04/22.

  1. 2008/04/22
    Bikeman

    Bikeman Inactive Thread Starter

    Joined:
    2008/04/22
    Messages:
    2
    Likes Received:
    0
    Alright, pulling my hair out here...
    What I`ve done so far..
    Tried ServU ftp server 7 and filezilla to make sure its not a software issue..
    set up on ports 1232 and later 65000, because ISP blocks port 21..
    I can ping the machine from a command prompt, and can access files thru the network..

    Network topology:


    Have a wrt54g router with ddwrt rev 23 sp2.. set up port forwarding for 21, 1232 and 6500 at appropriate times.. This router provides wireless internet to my main machine, which then has a network bridge set up on it to send the connection out my network jack to a netgear fvs318 router that is set up to operate as a switch only... which I then have 3 other computers connected to via hardwire.. All can access the machine hosting the ftp server in various ways but cannot connect to the ftp server on the machine.. Ftp is set up to be allowed in windows firewall... Any ideas folks??? Thanks,

    E.

    but I cannot connect to the ftp server either thru the local address on local network, or thru the internet from work, connection fails..
     
  2. 2008/04/23
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    If you can't connect to the FTP server from within you own network, this is not an ISP problem - it is local to your computer.

    OK, lets start at the beginning.

    First thing FTP is an unusual internet protocol in that it uses two ports rather than just one. Have a look at the IANA port number documentation for an authoritative confirmation of this. You'll see that port 21 is set aside for FTP, but also port 20 is used for FTP data. The way FTP works is that requests are made via port 21, but the actual data is passed on port 20.

    Because of this peculiarity, firewalls often have special rule-sets for FTP.

    So I suggest you do this.
    1. Reset the FTP server to it's default port settings (let's get it working the way it likes to work before playing around with port assignments)
    2. Next check that the server is opening the right ports. The simplest way to do this is probably to try accessing the following address in your browser on the PC running the FTP server:
      Code:
      ftp://localhost/
      This should give access to the files being offered (unless you've specifically set up the FTP server to only accept requests via a specific host name - if this is the case, try the test using this name instead of localhost). You should also see the ftp service listed as a listening port if you do a netstat -a at the command prompt. If this fail the problem is with the FTP service itself.
    3. Then try to connect from another PC on the local network. If that fails but the previous test passed, you are probably looking at a firewall issue. Check through your firewall settings and ensure that both ports 20 and 21 are correctly set. Also check your Anti-virus settings at AV programs can block ports to prevent trojans using them.
    Only after you've got FTP working internally should you start looking at how to provide it externally. Also notice that you have to change the assignment of both the ftp control and ftp data ports - and that they need to be different (i.e. don't set them both to the same alternative port number).

    Oh! and ISP's block FTP for a good reason - it is another way for someone to hack into your system. Make sure you secure that server! Use robust passwords. If this is a service you are running to a small number of users, consider offering the FTP connection over a VPN rather than directly opening the FTP server to the internet.
     

  3. to hide this advert.

  4. 2008/04/23
    Bikeman

    Bikeman Inactive Thread Starter

    Joined:
    2008/04/22
    Messages:
    2
    Likes Received:
    0
    Hi Reggie8,
    Thanks for the info, will try tonight... Can you give me some information on setting this up via VPN? I know my router supports it, just havent played with it...
     
  5. 2008/04/23
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Can you give us the make and model of your router.
     
  6. 2008/04/24
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    stupid question #1

    Are you configuring the ftp clients to use the ports other than 20 & 21?

    Also....why are you using a bridge? All you need to do to config the netgear router as a switch-only is to disable its dhcp completely, give it a static ip address, and set the default gateway to the lan ip address of the wrt54g.
     
  7. 2008/04/25
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    From the first post of this thread... ;)

     
    Last edited: 2008/04/25

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.