Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1826
  • Last Modified:

Filezilla Client/Server setup behind router(s)

I've installed Filezilla Client on a Windows 2008 server behind a Fortigate firewall which protects our domain.

I've installed Filezilla Server on a Windows 7 home computer.  This home computer is behind a public Static IP Address: 208.xx.xx.xxx on an AT&T modem that is set in "Bridged" mode to allow traffic to pass through to my own Linksys/Cisco router.  This home router handles DHCP for my home network.  Each computer on my home network has its own listening port as I need to access different home computers while away from my home on business.  The IP addressing scheme is:  192.168.x.xxx:3390.  3390 is the listening port of the computer on which Filezilla Server is installed.  My own home router has Port Forwarding enabled and set up correctly.

From the domain, Filezilla Client has already been used to connect to 3rd Party software vendors with whom I must transfer/received files occasionally.  Because of this, I feel the client software is already configured correctly.  In Filezilla Client, I'm using the Static IP address (208.xx.xx.xxx) in the "Host Name" field.  Username and Password fields are populated with the Windows 7 Home PC Username and Password.  I'm not sure what to put into the "Port" field, although I've tried the default 14147, 21, 3390 (listening Port of home PC), but nothing works.

I do receive "Connected to Server, waiting for Welcome Message", but no connection is ever established.

Please advise.
0
baleman2
Asked:
baleman2
  • 5
  • 5
  • 2
1 Solution
 
lruiz52Commented:
You can do two things;
You have to open port 3390 outbound on your fortigate firewall.

Or

change listening port on your FileZilla server to standard FTP port 21.
0
 
lruiz52Commented:
You can do one of two things;
You have to open port 3390 outbound on your fortigate firewall.

Or

change listening port on your FileZilla server to standard FTP port 21.
0
 
Dan CraciunIT ConsultantCommented:
3390 is usually the port for RDP, and I think your router is setup to allow connections on this port to allow RDP connections.
You can't use the same port for the FTP server and RDP, if they both run at the same time. I would suggest sticking with the default 21 for FTP and adding the NAT rule for it in the router.

HTH,
Dan
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
baleman2Author Commented:
Let me update some of my initial setting(s) info on the Filezilla Server.  When I click on the Filezilla Server icon to open it up, a popup is displayed that shows the default server IP address to be:  127.0.0.1.  The default port is:  14147.  

So, do either of these settings need to be changed before proceeding with your suggestions?

To lruiz52:
          Is it the default port just mentioned above that must be changed to 21?  Because, if I accept the defaults and allow Filezilla Server to open, I can then drill thru the Top Menu to: Edit->Settings and the default port that's listed there is 21.

To Dan Craciun:
          My home router has allowed me to "port forward" to 3390, 3391, 3392, and 3393 to specific home IP addresses (192.168.x.xxx:3390 thru 3393) in order to RDP from the outside world into my home network.  I'm not sure I understand if you're asking me to make a change in my home router or not?  More details, please.
0
 
Dan CraciunIT ConsultantCommented:
If the port Filezilla server listens to is 14147, then you must add a rule in your router to forward an external port (can be 14147 for simplicity, but not necessarily) to the internal IP of the server, on port 14147.

BTW, by default 14147 is NOT the port Filezila server listens to, it's the port for the administrative console. In other words, on that port you can only configure Filezilla, not see the files.

See FAQ no 3 here: https://wiki.filezilla-project.org/FAQ
0
 
baleman2Author Commented:
Attached is a screenshot of my router's "Port Forwarding" settings.  I've made entries (without enabling) that I think would cover all the possibilities.  Which one of these entries would allow connectivity, in your opinion?

Also, on the Filezilla Client, should I be using the Static Public IP address as the HOST field entry.  Would Username and Password be required on the Filezilla Client, i.e., Username and Password of the Filezilla Server or the Windows 7 PC itself?
0
 
Dan CraciunIT ConsultantCommented:
Attached?
0
 
baleman2Author Commented:
Sorry, that screenshot should be available now.
Screen-Shot-03-23-14-at-03.51-PM.PNG
0
 
Dan CraciunIT ConsultantCommented:
Check the box where it says "Enabled". Right now, you added a rule for ftp on your router but it's not active.
0
 
baleman2Author Commented:
Purposely unchecked in the screenshot.  I'd already tried to connect when it was checked and couldn't make a connection.

Can both the FTP and RDP ports be forwarded to the same internal address?  Take a look at RDP1 in the screenshot - 3380 is already forwarded to 192.168.1.25.
0
 
baleman2Author Commented:
3389, typo on my part.
0
 
Dan CraciunIT ConsultantCommented:
Nope. Only one application can listen on a port.

Did you make an exception for Filezilla Server in Windows firewall?

You can check if you can connect to the server from inside your local network.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now