Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 4 subscribers
  • Views 19889 views
  • Users 0 members are here
Options
Suggested
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

Brad Field

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

    Because only the destination port ist 21 for ftp or 80 for http.

    The client port is nearly everytime one of the >1024 ports.

    Or am I understanding anything in your question totally wrong?

    Gruß / Regards,

    Kevin
    Sophos CE/CA (XG+UTM), Gold Partner

  • 0 in reply to kerobra_retired

    I think I understand: the source port is irrellivant? I have a Firewall rule setup to allow the destination IP over the destination Port, but it is still dropping. The only thing I could see that wasn't covered in the rule was the source (client) port. I am just trying to figure out why, within the last week, this has stopped working.

Reply
  • 0 in reply to kerobra_retired

    I think I understand: the source port is irrellivant? I have a Firewall rule setup to allow the destination IP over the destination Port, but it is still dropping. The only thing I could see that wasn't covered in the rule was the source (client) port. I am just trying to figure out why, within the last week, this has stopped working.

Children
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?

Unfiltered HTML