Running Filezilla Server on Multiple Computers on Same LAN
Posted: 2010-05-16 03:23
I have installed Filezilla on two computers on my office LAN. For discussion, we'll call them \\Alpha (192.168.1.5 on LAN) and \\Beta (192.168.1.65 on LAN). Everything works perfectly on \\Alpha (even connecting from outside the LAN, but I can't connect to \\Beta even from inside the office LAN
\\Alpha is listening on Port 21. \\Beta is listening on Port 2121.
\\Alpha and \\Beta passive settings are both set to default.
My office router port forwarding is set as follows:
* TCP Port 21 is forwarded to \\Alpha
* TCP Ports 10000 to 11000 are forwarded to \\Alpha
* TCP Port 2121 is forwarded to \\Beta
* TCP Port 11001 to 12000 are forwarded to \\Beta
Not only am I unable to connect to \\Beta from home, I can't even connect to \\Beta from within my office LAN (using 192.168.1.65:2121 as the address). I can't even connect to 127.0.0.1:2121 while on \\Beta.
I've looked at the AVG firewall running on \\Beta and it seems to be set correctly. The Filezilla Server application is set to "allow for all.
What am I doing wrong? I have read the FAQ at the top of this forum, including these statements:
# I'm behind a firewall and nobody can connect to my server or transfer files / directory listings
You have to configure your firewall to allow incoming connections on the ftp port (default: 21), as well as allowing outgoing connections from the server. FileZilla Server tries to use a port one less than the ftp port for outgoing connections. If that fails it tries to use a port one larger than the ftp port and after that it requests a port from windows. It may be best to allow all outgoing connections from the server.
Further you have to allow a port range for incoming connections for passive mode transfers. You can specify this port range on the "passive mode settings" page in the settings dialog in the server interface. In most cases, a range like 5000-5100 is sufficient.
With certain firewalls, it may be possible that FileZilla can't determinate the external IP address. In this case you have to enter the IP address (or your host name) on the passive mode page in the settings dialog. In case you've a dynamic IP (most dialup users), you can also chose to retrieve the ip address from a website.
# I'm behind a router and nobody can connect to my server or transfer files / directory listings
You have to configure your router to forward the ftp port (default: 21) to the server machine.
Further you have to forward a port range for passive mode transfers. You can specify this port range on the "passive mode settings" page in the settings dialog in the server interface. In most cases, a range like 5000-5100 is sufficient.
Most likely, FileZilla can't determinate the external IP address if behind a router. In this case you have to enter the IP address (or your host name) on the passive mode page in the settings dialog. In case you've a dynamic IP (most dialup users), you can also chose to retrieve the ip address from a website.
I've read and re-read them and checked and re-checked my settings on Filezilla Server on \\Beta, the firewall on \\Beta and the office router. Obviously, I'm doing something WRONG, but I'll be darned if I can see what it is. Can you?
\\Alpha is listening on Port 21. \\Beta is listening on Port 2121.
\\Alpha and \\Beta passive settings are both set to default.
My office router port forwarding is set as follows:
* TCP Port 21 is forwarded to \\Alpha
* TCP Ports 10000 to 11000 are forwarded to \\Alpha
* TCP Port 2121 is forwarded to \\Beta
* TCP Port 11001 to 12000 are forwarded to \\Beta
Not only am I unable to connect to \\Beta from home, I can't even connect to \\Beta from within my office LAN (using 192.168.1.65:2121 as the address). I can't even connect to 127.0.0.1:2121 while on \\Beta.
I've looked at the AVG firewall running on \\Beta and it seems to be set correctly. The Filezilla Server application is set to "allow for all.
What am I doing wrong? I have read the FAQ at the top of this forum, including these statements:
# I'm behind a firewall and nobody can connect to my server or transfer files / directory listings
You have to configure your firewall to allow incoming connections on the ftp port (default: 21), as well as allowing outgoing connections from the server. FileZilla Server tries to use a port one less than the ftp port for outgoing connections. If that fails it tries to use a port one larger than the ftp port and after that it requests a port from windows. It may be best to allow all outgoing connections from the server.
Further you have to allow a port range for incoming connections for passive mode transfers. You can specify this port range on the "passive mode settings" page in the settings dialog in the server interface. In most cases, a range like 5000-5100 is sufficient.
With certain firewalls, it may be possible that FileZilla can't determinate the external IP address. In this case you have to enter the IP address (or your host name) on the passive mode page in the settings dialog. In case you've a dynamic IP (most dialup users), you can also chose to retrieve the ip address from a website.
# I'm behind a router and nobody can connect to my server or transfer files / directory listings
You have to configure your router to forward the ftp port (default: 21) to the server machine.
Further you have to forward a port range for passive mode transfers. You can specify this port range on the "passive mode settings" page in the settings dialog in the server interface. In most cases, a range like 5000-5100 is sufficient.
Most likely, FileZilla can't determinate the external IP address if behind a router. In this case you have to enter the IP address (or your host name) on the passive mode page in the settings dialog. In case you've a dynamic IP (most dialup users), you can also chose to retrieve the ip address from a website.
I've read and re-read them and checked and re-checked my settings on Filezilla Server on \\Beta, the firewall on \\Beta and the office router. Obviously, I'm doing something WRONG, but I'll be darned if I can see what it is. Can you?