A colleague needs to access ftp.sophos.com (220.127.116.11) using Filezilla as their SFTP client, via TCP port 990. I set up the security policy rule as follows:
They could not log onto the ftp.sophos.com site. The password credentials they used are correct. Is the rule set up correctly? On a Cisco ASA I would have used the following ACL:
access-list aclinside extended permit tcp any host 18.104.22.168 eq 990
Any advice is much appreciated.
I've had to add the SSH application to many SFTP rules, as the firewall usually sees that. Look in your Unified Logs and it should show you why it was denied.
Like @DPoppleton mentioned what do the deny logs say is the reason for traffic being stopped? What is the FW seeing?
That screen shot shows the application as FTP, which means the FileZilla client isn't encrypting. The client may need to be set to use SFTP (and the firewall will see that as SSH, so you will need to add that application to your rule.)
Thanks for your reply again. I have now added SSH under Application within my rule.
I will have the user test.
@DPoppleton, forgot to mention that the Filezilla client was configured for SFTP and was tested on a ADSL line and the user was able to connect fine.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!