Problem setting up local FTP host

[Doug]

I have three XP Pro systems networked behind a Netgear RP614 four port
router fed by Comcast thru a Motorola Cable Modem. Everything on the LAN
side is fine, full mutual file/printer sharing and Internet access. I want
to set my system up as a FTP local host where by my friends and family
members can access specific folder/files on my computer. I have port
forwarded 21 to my IP address. I have also setup third party (SERV-U FTP
Server)software that listens to port 21 and acts as a local file sharing
host. At the point someone attempts access, they are confronted with
request for a user name and password for access. These are preset by me. The
problem starts here, when attempting initial penetration the connection is
refused or unavailable. I can ping everything on the LAN side fine. When I
try to access the router from the WAN side - no way. I can do port query
from a host site such as http://www.grc.com/ and am given a report that port
21 is open, everything else is stealthed. Even though the port is open it
will not reply to a ping or accept any packet exchange. This WAN side
attempt is done by using my Internet IP. This is the only way for outside
sources to access my router. I have Norton Internet Security 2003 all set
with the appropriate rules to allow the specified hits through in both
directions. The XP firewall has been totally disabled - Still nothing.
Everything on the LAN site, again, is great. By try as I might, using the
FTP// InternetIP - I can't establish contact. I even tried a freebie Net
host, www.NO-ID.COM and did a web redirect to me using a domain name instead
of the IP. This would be easier to remember and use. Still nothing. If you
have made it this far, any clues or suggestions would be GREATLY
appreciated - Thanks
Doug

 

[Guest]

This might help you out it came straight from RhinoSoft.co

FTP Client Cannot See Directory Listings or Connect

Sometimes ISPs prevent their customers from running FTP servers by preventing access on the FTP port, number 21. They "listen" to the traffic on this port and disable directory listings or file transfers, or they disable use of this port on incoming connections all together

Some customers have learned that by changing the port that Serv-U listens on from port 21 to some other lesser known port number, they can allow access to their FTP server

Your best bet is to try using ports above 1024 first, such as port 2121, or using other ports below 1024. To find out for certain it is recommended to try different port settings

NOTE: You must also change your port number in your FTP client. In FTP Voyager you can change the port number in the "Advanced" settings for your site profile, under the "Connection" category

In addition, running an FTP server may violate your agreement with your ISP. Please ask your ISP for permission before making any of the suggested port changes

NOTE: When testing Serv-U we recommend using FTP Voyager because of its logging capabilities, and our ability to support both Serv-U and FTP Voyager.

 

[Dennis]

maybe you can download FtpTerminator at http://www.soft2004.com to
help you. It is very easy to connect to a ftp sever by using
Connection Wizard.