This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Filezilla Cannot Connect to Server

I have been trying to figure this one out.

I have Host Definition for FTP Server IP Address

I have firewall rules setup to allow traffic from all of my networks across any service to FTP definition.

Firewall keeps Dropping and records random numbers on srcport. The entries are correctly identifying my IP, IP I am connecting to, and dstport: 21. Why is it using a random port number for the source port.

This thread was automatically locked due to age.

Parents

0 Brad Field over 8 years ago

Here is a screenshot of the rule I have setup. I have tried this with more focus on the Service (FTP, File Transfer, etc.) but always end up with the same result: Cannot Connect to Server.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 8 years ago in reply to Brad Field

So, do you confirm that "GoDataFeed" is bound to 'Interface: <<Any>>' and not a specific interface?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 8 years ago in reply to Brad Field

So, do you confirm that "GoDataFeed" is bound to 'Interface: <<Any>>' and not a specific interface?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Brad Field over 8 years ago in reply to BAlfson

Yes, the definition for GoDataFeed is bound to interface:<<Any>>. I double-checked a few of my definitions yesterday to be sure I was not limiting them by binding to an interface.

Brad
Cancel
Vote Up 0 Vote Down

Cancel
0 kerobra_retired over 8 years ago in reply to Brad Field

2017:03:17-12:40:46 cschadwick ulogd[17716]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop"
fwrule="60002" initf="eth0" outitf="eth1" srcmac="00:::::07" dstmac="00:::::98" srcip="192.168.XX.XX" dstip="72.4.XX.XX" proto="6"
length="52" tos="0x00" prec="0x00" ttl="127" srcport="39326" dstport="21" tcpflags="SYN"

Where I am quite unsure... is the Filezilla Server an internal FTP Server (where you are trying to connect to over a dyndns or whatever URL) or is that a completely external FTP Server?

Gruß / Regards,

Kevin
Sophos CE/CA (XG+UTM), Gold Partner
Cancel
Vote Up 0 Vote Down

Cancel
0 Brad Field over 8 years ago in reply to kerobra_retired

This is a completely external ftp server. I have the same situation in two different locations, both use Sophos SG230 and both have rules to allow the traffic and have worked up until recently. The only thing that has changed is an upgrade to the current firmware 9.411-3. I am stumped.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 8 years ago in reply to Brad Field

I wonder if this doesn't have something to do with a tightening of SSL. I had an issue earlier today. After fighting it for an hour, I downloaded a new version of WinSCP, chose an upgrade of the existing installation and then everything worked fine. What happens if you get the latest version of FileZilla?

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 Brad Field over 8 years ago in reply to BAlfson

It was worth a shot, but no luck. Same result with the latest version. I was hoping because one of the fixes in the newer version was a change to timeout settings.

I have a case open with Support now. We will see what we can figure out.

Brad Field
Cancel
Vote Up 0 Vote Down

Cancel

Filezilla Cannot Connect to Server

Submitted a Tech Support Case lately from the Support Portal?