FileZilla (server)

Shaun · 03-08-2004, 14:30

I've decided to have a bash at running an FTP server at home, I'll probably get a spare comp to run it on when I get chance but until then I thought I'd have a go at getting it up and running.

I've set it up fine with a test folder to share and I can connect locally using IP 127.0.0.1 however I cant get it to connect with either my local IP address 192.168.1.2 or my external one!

I'm running XP home and no software firewall, as there is one on the wireless router (dlink G604T). I'm at a loss as to why I can't log on, I've set up port forwarding and opened port 21 on the router but I still cant connect.

Have you guys got any ideas?

UPDATE - After a restart I've managed to connect to my local IP address (192.168.1.1) but still can't access it from my external IP!

Stuart · 03-08-2004, 14:49

Once you have ensured Port 21 is open at your firewall (I know you probably have, I just want to check), you may need to connect your FTP clients using passive connections (there should be an option in the program to do this).

Normally FTP uses active connections. What this means is that the FTP server will recieve a request to connect on port 21. Once it has found out the IP of the connection computer, it drops the connection and opens one on a random port. If it can't establish a connection on a random port, you won't be able to get in. It can be a bitch to configure firewalls to allow active connections.

If the FTP client requests a Passive connection, the ftp server will happily talk to it on port 21.

Shaun · 03-08-2004, 15:05

I ran Shields up and that showed port 21 to be open and I've double checked the router has port forwarding enabled to this computer on port 21. I've also set filezilla client to passive mode but it still says unable to connect!

Although an article on no-ip.com I just read said that some routers won't allow access to a server held on a home networked PC from that or any other PC on the network via an external IP! So maybe I'll have to wait until tomorrow to test it from my grandparents PC!

Richard M · 03-08-2004, 15:31

Doesn't FTP negotiate connections on port 20 and only use 21 for the data transfer?

Shaun · 03-08-2004, 16:13

Quote:

Originally Posted by Richard M

Doesn't FTP negotiate connections on port 20 and only use 21 for the data transfer?

Well I thought I was sorted but as you say port 20 seems to be used for data so does this mean that I need to port forward this too?

I've found a discription here:http://slacksite.com/other/ftp.html#basics

Some of it is a bit technical for me though

Stuart · 03-08-2004, 16:27

Quote:

Originally Posted by dellwear

Well I thought I was sorted but as you say port 20 seems to be used for data so does this mean that I need to port forward this too?

I've found a discription here:http://slacksite.com/other/ftp.html#basics

Some of it is a bit technical for me though

Whoops, looks like I got the FTP process ar*ahem* backwards...

if port 20 is used for data, you will need to forward that as well..

Shaun · 03-08-2004, 16:54

I'm attempting to get this dam router to open port 20 too so I'll let you know if this works!

Shaun · 03-08-2004, 19:45

Well I'm having SO much trouble trying to get my router to p
open port 20 (or any other port other than 21 actually) I just cant understand it and neither can dlink!

So until I get this port opened it looks like I'm buggered, there goes the idea of tinkering with a pop3 server too!

poolking · 03-08-2004, 20:30

What's the make of the router?

Shaun · 03-08-2004, 20:46

its a dlink g604t

poolking · 03-08-2004, 20:48

The reason for asking, I had a belkin router and had allsorts of probs, in the end I just dumped the router and the server worked fine.

Shaun · 03-08-2004, 21:03

I'm hoping to find out from Dlink what the problem is, one article I've read said that I need to turn off the DCHP server and assign IP's manually, which looks a night mare and I'm a little reticent to start fiddling as everything else is working fine a the the moment!

No matter how I try and set the access and port forwarding the router says the port is open but shields up says its not.

Bloody computers

Stuartbe · 03-08-2004, 21:05

Are you running a local firewall on the host machine or have the xp firewall enabled ?

Shaun · 03-08-2004, 21:24

Quote:

Originally Posted by Stuartbe

Are you running a local firewall on the host machine or have the xp firewall enabled ?

Both turned off, I only keep NIS installed for the parental controls and pop up/ad control, but I disabled it all while I was playing.

Just cant seem to understand it, maybe the routers buggered? Dlink said that they'd get back to me on it, I'm not hopeful though.

IMplODemE · 03-08-2004, 23:15

Seperate this issue. I assume that you have 2 PC's, one being a Filezilla Server, the other acting as a Client trying to connect to the server machine. ***If you are trying to connect to the internal IP from the same exact machine, the router/switch that you have may cause errors. I have this issue with a Linksys.

Example: If you can't get to it from one local machine to another, Client(192.168.1.5) and the Filezilla Server(192.168.1.2) then this will have nothing to do with the outside world, or the port forwarding that the router does for incoming requests.

Leave DHCP on the router enabled, take the server and set a STATIC IP for it, I suggest something like 192.168.1.120

Try connecting to the Filezilla server from a different computer.