Need help setting up an FTP Server!

[Dolemite69]

First off:

I am using WinME, FTP Serv-U v2.5h, and have a Kingston Internet Gateway 4-port Router.

I am trying to setup an ftp server but it's giving me hell. I think all of my problems are coming from the router side, but i am clueless of what to do... Anyone have any ideas? Sorry for being vague, but I don't know what kind of info is needed..... just let me know. ~Thanks!

 

[sadb0i]

if u are using ftp serv u i think it does everything automatically for you...whats happening when u try to log in????

 

[frizzlefry]

I'm guessing that the router has some built in firewall. Or you have to open specific ports on the router. Usually FTP uses port 21 and you just need to config the router to have this open. I think I correct on this, correct me if I'm wrong.

also do you have any software firewalls installed? you would need to config these as well. I used servu and setup to only allow specific IPs to login. You also need to config users with servu.

 

[bevancoleman]

Unless it's a fairly smart firewall/gateway, clients may only be able to connect using PASV mode

 

[ProviaFan]

I'm no expert in this, but wouldn't you need to open port 21 on the router, and then have all requests coming to that port forwarded to the computer running the ftp server (I'm assuming you're using NAT or something here to share one IP). HTH.

 

[Cenalian]

I'm pretty sure jliechty is right here. By default, port 21 SHOULD be open on a router. You just need to set it up so that all requests for that port (or whichever port you decide to use) are auto-forwarded to that specific computer.

 

[JeffreyLebowski]

Is your internet connection a static ip or dynamic? If dynamic i.e. it changes everytime you log on then you'll need to use a service like dns2go so when the machine starts up it logs its IP address with the DNS2go servers so people can connect.

Then in the router set up the port21 forwarding to the machine that is running the FTP.

 

[bevancoleman]

Most of thoses little firewall devices allow port forwarding or redirection. Some also allow a machine to be defined as a server, I assume this means all ports get redirected to it.

For thoughs who don't know what the diff between a standard FTP and a Pasive FTP connection


Normal
1 - Client contacts server on 21 (control channel)
2 - Client logs in
3 - Client issues PORT command requesting a data chanell, the server responds with the port number (often random or from a pool).
4 - Client issues other commands....
5 - Client issues file transfer/ directory list or other command that requires data transfer
6 - Client connects to the port given by the server in 3
7 - Data is transfered, often the data chanell is closed again (but left reserved for more connections)
8 - etc...


Pasive
1 - Client contacts server on 21 (control channel)
2 - Client logs in
3 - Client issues PASV command with a port number as a paramater (often random or from a pool, this is only the clients side). The server responds with an acknologement (or not).
4 - Client issues other commands....
5 - Client issues file transfer/ directory list or other command that requires data transfer
6 - Server connects to the port given by the client in 3
7 - Data is transfered, often the data chanel is closed again (but left reserved for more connections)
8 - etc...

As you can see the only change is the direction of the data chanel, most firewalls will allow outgoing connections but not incomming connections (unless open port). A firewall that will allow PORT need to be monitoring the control chanel for PORT commands, and most don't.

There is one other way to allow standard FTP, as the data ports are always >1024 many firewalls leave the high ports open.