GuildFTP probs *GETTING THERE* Port 21 now open, see original post, please!

[MichaelD]

OK, I'll try to be as concise as possible. Per Need4Speed (who I realllly hope comes back to my thread!) I checked out the other services and came up with the following results:

1. I updated my router (Netgear RT314) firmare to the latest version, zeroed out the settings, then set it up for my internet connection, but didn't change stock filters.

2. IIS was using Port 21. IIS has been removed from the system

3. Because of #1, GuildFTP sees Port 21 now and the "server" runs normally

4. I cannot see my FTP server via my public IP, but possibly b/c my router doesn't allow "loopback" i.e. go outside my LAN, out into the internet, to come back into my LAN via the same IP

5. My GF, who is outside my LAN cannot see my server via my public IP either, but

6. My GF CAN ping me. Perfect ping, 84ms round trip, no loss

7. When I try to access my server via it's internal IP, I do get the dialogue box, and when I put in a username/password, the "Current Connections" dialogue box on the server flashes for a split second, the info of the IP trying to connect, but then it dissappears. (I have the server and it's monitor right next to my main rig) The port lights on my router also flash accordingly...the packet is getting there, but "dying" upon impact...

8. I tried setting the FTP port 21 filter to "Action Matched = Forward" Met with #7 above.

9. Tried setting the port forwarding for Port 21 to "ALL" instead of "LAN" met with #7 again.

10. Tried various combinations of filters...#7.

Help.

__________________________________________________________________________________________________________________________________________
I'm very confused. <--what else is new?

I setup GuildFTP on my server. I configured it, as per the instructions. When I "Start Server" from within the FTP proggy, I get "Could not open port 21, pick another port."

For kicks, I tried logging in as anonymous and admin, with no connection whatsoever.

I went into my router (Netgear RT314) and checked for port 21 forwarding. I have the filter set to "match port number exactly". It looks good to me.

So, I went to DSLreports and did a security scan. According to them, my PORT 21 is wide open. What is going on here?

This is right off my results report:

tcp21
(help) comment attempting anon ftp to ftp server.. (you should log this ftp attempt).
do you accept ftp connections from any machine? does your ftp server allow anonymous access? can anonymous users _write_ files anywhere within it? does the ftp welcome message give away the ftpd version? public ftp servers contain readable binaries which reveal your machine type.
result Could not talk to the FTP server
FTP server noticed.
open ftp port.
score Points Deducted:10

Notice it says "FTP server noticed/open FTP port?"

I'm really sad about this...I've been looking forward to having my FTP up and running for a long time now...help please.

 

[ScottMac]

You may also need to open port 20.

Also: Check your settings, some FTP applications like to use "Passive" mode, others do not.

Good Luck

Scott

 

[spidey07]

sounds like you already have an FTP server running. GuildFTP is telling you another app owns port 21.

What OS are you using?

 

[MichaelD]

Thanks guys. I'm running W2K Pro w/all the SPs and updates.

I do not ICP or chat or any of that stuff.

Here's my entire scan:

DSLreports security scan

 

[MichaelD]

Bump. i've been messing with the filters on the router....nothing has changed...I'm beginning to wonder if it's GuildFTPand not the router?

I even went into Admin/options/advanced and tried the PASV thing so I could login from within my network...that didn't work either.

 

[MichaelD]

And again...ttt.

 

[MichaelD]

Morning bump.

 

[Need4Speed]

sounds like you got multiple issues going on.

First you need to figure out what app is using port 21 other than guild FTP. Is it possible that IIS is running?

Once you get that figured out, I would recommend that you update your router firmware to 3.25, if its not already. Load the default config that is downloaded with the new firmware. it makes some of the basic filters much easier to use without compromising security.

once all that is worked out and you have port 21 cleared for guildftp, then you can start to figure out how to get through the router.

My recommendation to you is the follow these steps:
1. Determine whats using port 21 and shut it down.
2. Get guild ftp to work on your LAN..ie log in from another machine or from the localhost.
3. update/config router to base settings

only then would i start to work on getting in from the WAN side. There are a lot of things to consider once you get to that point. A lot of it will depend on the clients that connect to the server. Some can handle the PASV/PORT issue much more elegantly than others....first things first....get ftp working on lAN

 

[MichaelD]

Thank you, Need4Speed. It appears I have a lot of work to do. I'll start checking things when I get home today. Thanks a lot, man.

 

[MichaelD]

TTT, please see original post. I'm getting there, but need some professional help...didn't sound right, but you KWIM.

 

[Tallgeese]

Here goes:

* While troubleshooting this issue make sure inside access is working first. Once you can hit the FTP internally, THEN you can attack the RT314 config for external access.

* Has this machine ever had ANY other FTP server software loaded on it (besides IIS)?
* Has this machine ever had ANY software-based firewall loaded on it?
* Has this machine's network configuration ever been set for IP Security or TCP/IP Filtering (Under "Advanced"->"Options" area of TCP/IP for your Local Area Connection)?
* Have user accounts been configured for GuildFTP?
* Does this machine have a modem?


From the GuildFTPd website support area:

2. Determine whether or not the problem is GuildFTPd by itself or how you've set up the PASV support between GuildFTPd and your Internet Sharing Device.

A. Install a FTP client on the same computer you have GuildFTPd installed on.
B. Connect to the server using the GuildFTPd computer's IP address, NOT your router/firewall's IP address.
C. Make sure to NOT use the PASV or passive option in your FTP client. You want this connection to be active.
D. Make sure to use the correct port you set GuildFTPd up on (This isn't the passive ports, this is the port in the OPTIONS tab.).
E. Connect to the server.

If you can connect to GuildFTPd on the same computer, but can't connect from a computer outside of your personal network, there's a problem in either GuildFTPd's Advanced server options or in your router/firewall setup.

A. Double check your settings in both. Make sure you've got the correct ports forwarding to the IP address of your GuildFTPd server and make sure that GuildFTPd is using the same port range. GuildFTPd also needs to be configured with the WAN or Internet IP address of your router for it's Passive IP setting.

B. You may need to upgrade your router's firmware in order to be able to set up a range of ports to be forwarded to your server.

C. Make sure that you're trying to connect to the IP address of your router from outside your network and not the address of the GuildFTPd server.

If you can't connect to GuildFTPd on the same computer, troubleshoot the error you're seeing using tips on this chart or by researching the help file included with GuildFTPd.

 

[MichaelD]

Thanks, TallGeese. I'm looking into all this. Depressed as hell, but looking into it. I'll get there.