Yesterday morning (November 16th), I was able to FTP into the two external sites that we use for hosting without issue. Later on in the day, I tried (I use Filezilla) and when trying to connect to either of them, it gives me the following message -
Status: Resolving address of ADDRESS
Status: Connecting to XX.XX.XX.XX:21...
Status: Connection established, waiting for welcome message...
Status: Insecure server, it does not support FTP over TLS.
Status: Server does not support non-ASCII characters.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT XX,XX,XX,XX,XX,72
Response: 200 PORT command successful.
Command: LIST
Response: 150 Opening BINARY mode data connection for /bin/ls.
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
If I disable the firewall component in Avast, the FTP connections go right through without issue, as they had earlier in the day. This also affects using the built-in "
ftp://address" access in Windows 10 (1709).
Did anything change to impact this? I can't even find the firewall logs anymore (which I used to diagnose other firewall related issues a couple months ago) within the client. I went into the cloud console and didn't see anything out of the ordinary, with the exception that there were no entries for FTP in the "Advanced Packet Rules" tab. I added that in, but it still will not function with the firewall enabled.
Ideas? We have the "Avast for Business - Premium Endpoint Security" product that is cloud based.
