Recent FTP Issues with Avast Firewall?

zlamare · 2017-11-17T15:00:04.000Z

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.

zlamare · 2017-11-17T21:21:21.000Z

I just tried remotely connecting into my device from outside the building with Teamviewer, which has always worked, and it fails to connect (even though it shows the device as online in my list). I was able to RDP into a server within the network (Avast Firewall is not available for server), but could not RDP from that machine into my device.

Once I turned the firewall component off in the cloud console and waited a few minutes for everything to sync up, I could connect via Teamviewer from outside and RDP through the other machine. Once I connected via RDP, I had a prompt to allow or deny the Teamviewer connection (I manually set it to ask, not auto-decide, earlier), even though I had previously added specific rules for the application and it was also working up until yesterday.

Something definitely changed in the firewall component of Avast.

AnotherUsername · 2017-11-21T23:21:27.000Z

Do you know what version your clients are on?

zlamare · 2017-11-27T13:47:47.000Z

AnotherUsername post:3:

Do you know what version your clients are on?

Current version - 17.7.2526 (build 17.7.3660.244)
Release date - 10/17/2017 8:35:56 AM

Set to automatically update.

zlamare · 2017-11-28T18:02:08.000Z

Updated to version 17.8.2527 (build 17.8.3705.249) and the issue persists.

Announcements