Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on March 30, 2017, 07:31:17 PM
-
Hello,
After update my Avast Premier to 17.3.2291 (build 17.3.3443.0) all local IP Adresses 192.168.1.* are blocked. Can not connect to them or to do a PING. I can't connect to my NAS and the rest of my devices.
Please Help. I don't changed anything only update. I have to deactivated the Avast Firewall to work.
OS: Windows 10 64 bits.
Thank so much.
-
Any change if you try this and reboot? >> https://www.avast.com/faq.php?article=AVKB204#artTitle
-
Thanks.
Done but nothing has changed ... The problem continue.
-
I'm having same issue and no fix, other than turning all the Shields off, seems to work. I have updated to build 17.3.3443.0 with no change.
-
Is it the Firewall or the Web Shield which is causing the issue?
-
The firewall. I can browse any public URL with no problems. It's only in the local IP 192.168.1.*
I have checked the "allow friendly net in Private" (sorry i don't know the name of this option in english) but not work too.
The range 192.168.1.0 - 192.168.1.255 is in the "Friends" option.
Thanks.
-
That seems to depend on the mood Avast is in. Sometimes it's one, then again next time it's both, then next time it's the other. This was never an issue until the update of two days ago.
-
Could you both run an Avast repair and report back if the issue is resolved?
-
NO Change!
-
Have similar issue. Avast blocks access to my router! I thought that it is a router problem and was thinking to buy a new one! I can login to my router but after few seconds it gets unresponsive.
P.S. Have to disable automatic port scan detection to make it works...
-
I've reported the issue to the Avast devs.
The firewall is not running in public mode, correct?
-
Hello,
Can you please post in what mode is your Firewall profile (public/private) when you have the issue?
Also knowing your OS helps a lot, since there are differences in Firewall on different OSes.
However the best option to pinpoint the issue would be sending us some debug logs.
Please enable debug logging in Settings > Maintenance > Enable debug logging
And complete Firewall logging in FW component settings > Advanced > Log all blocked packets
After setting this, please reproduce the issue and send us the following logs:
"C:\ProgramData\AVAST Software\Avast\log" folder
"C:\ProgramData\AVAST Software\Avast\fw" folder
"C:\ProgramData\AVAST Software\Avast\Fw.db" file
You can then send them zipped to braun@avast.com
Thank you very much,
Filip
-
Alternatively, you can check Firewall logs (Firewall page > Firewall logs).
Switch to "Show log for:" Rules
And if you see a message like "Firewall has automatically blocked IP address: <IP_addres> [Port scan detection]"
It means that there was a port scan done from the <IP_address> and Firewall blocked all communications from that address for 30 mins.
Port scan protection is by default turned on, but can be turned off in Firewall settings > Advanced > Port scan detection.
Filip
-
I put my OS in the first message:
FW in Private mode
OS: Windows 10 64 bits.
I will do some bug logs and will send you,braun@avast.com
Thanks
-
I had "And if you see a message like "Firewall has automatically blocked IP address: 192.168.1.- [Port scan detection]" in the rules report.
I turned off in Firewall settings > Advanced > Port scan detection yesterday.
The problem persist.
-
Filip,
Stopping the Port Scan Detection seems to have done the trick for my issue. With the Firewall turned on all my LAN devices can be accessed.
-
My NAS is blocked too, and I spent hours trying to fix various things on the PC and the NAS yesterday and today on one computer, to no avail. And then my own computer started doing the same thing today after Avast updated and sure enough, the firewall is again the problem. I have been a loyal Avast customer for probably over 10 years, and have recommended it to a lot of others over the years. But the firewall has given me more and more issues over the past couple years, blocking some essential software, like most of the Adobe CC suite, as well as others.
With this last update, they have removed several important features like opening the firewall to the private network, and editing or adding to the 'friends' list. And the application rules don't say default public/private now, but default medium risk work zone whatever that means. Nothing I have tried will allow me to get past the firewall to access some of the local network devices for more than a little while. And this is happening on two different Win 10 systems here, and just in the last day or so since the updates.
I spent nearly an hour on the phone with support, and the experience was poor. I have nothing against people in other countries, but it was tough to understand the thick accents and listen to the slow, halting English. I don't think the person 'reviewing' my PC hardly knew what to look at. She did not check any of the firewall settings! She just looked a little bit at the firewall application rules window I happened to have open, and scrolled up and down a bit, slowly, once in a while, almost aimlessly. If she was supposed to know something, or even be acting like she knew something, she needs better training. She opened the programdata folder just long enough to see the empty McAfee folder from the bloatware I uninstalled the moment I bought the computer, and that was enough to try to sell me a support package.
A computer tech would never have stared at some of this stuff for five minutes while I was on hold, but would have gone looking through the some of the specific listings, looked at settings, or event logs, or at very, very least looked at the firewall settings pages! When I balked at buying a $199 support package, they put a somewhat more skilled tech on the line, and then he looked through the registry long enough to find an old McAfee entry, and again, it was time to buy. Finally, he asked if I had tried reinstalling Avast, that maybe that would fix it, as the last item. I've dealt with some support people along the way, and I suspect that if some quick fix or two doesn't work, I am either going to be told that my NAS is the fault, or be told to reinstall Windows. I don't need to pay $200 to be told to reinstall Windows.
Ironically, my Avast Premiere multi-license is set to renew in 12 days, hmmm. I am disappointed - I am a paying customer, and have been for a long time.
That said, I have now disabled the port scanning, and maybe that will do it. Or maybe they will patch some bug, or just bring back enough control to open the private network and I can keep using it. I think it does work at protecting - at least to the best of my knowledge, it has not let nasties through in all the years I have had it.
-
Hi everybody,
I have the same problem as you.
Without knowing the existence of your thread, I opened this thread:
https://forum.avast.com/?topic=200131.0
Except the good will of some peoples that I thank again, I found no solution.
More precisely, I found again mt NAS after disabling for some time as well the anti-virus as the firewall and activating the standard Windows (10 in my case) firewall.
I think that the Avast team has to make an acceptable answer. I'm not sure if they are following the forum.
In any case, I propose to the Moderator to contact Avast in order to have a comprehensive position on this topic.
Best Regards,
Ioan
-
Please admins, combine all threads about this bug.
Example: https://forum.avast.com/index.php?topic=200108.0
-
Except the good will of some peoples that I thank again, I found no solution.
Try the workaround in Reply #12.
-
Thank you very much Asyn,
Unfortunately, the only one issue I found is to fully disable the Avast firewall and antivirus.
I'm enough angry, although I understand that sometimes some soft improvements are accompanied by heavy side-effects...
However we as users are waiting on a minimum advertising to keep us positive and confident.
Best Regards,
Ioan
-
Unfortunately, the only one issue I found is to fully disable the Avast firewall and antivirus.
Could you please send your logs to Filip then..!? (Instructions in Reply #11)
-
Thanks Asyn,
I've send that files to Filip
-
As an addition to my reply #16 above, I am getting a large number of entries in the firewall logs - blocked traffic. It would rarely have an entry before this update, but now I am getting around 1600 entries per hour, or about one every two seconds. Almost all of these just say 'system' and 'no rule found. I've tried 'show application' and then completely opening up the system application, but it keeps getting changed around or back to previous settings (even though it says 'no rule') and the log entries continue. This is very unusual, because I would check this, and get entries almost never, less than a page full for months. Example of event list attached. 192.168.1.1 is of course the router, .21 is the TV, my machine is .7, my Synology NAS is .6, and a brother printer is .3 - and there are quite a few other computers and mobile devices on the network as well, perhaps on average a dozen or so at a time.
Is there something I can/should do to try to normalize this?
-
Would you mind also capturing the firewall logs on the right side, where it says "Rules"? This may give a bit more of a clue on what the Avast Firewall is complaining about.
Thank you!
-
I've reported the issue to the Avast devs.
The firewall is not running in public mode, correct?
I have exactly the problem being reported here.
I have two WD NAS units (192.168.0.10 & 92.168.0.12) on my network. I now have to switch off the Shields to get them to work.
My Avast Internet Security is in Private mode, I have done the repair, I am running Windows 10.
This appears to be a common problem.
Not happy as I have wasted two days on this. Maybe time to change.
-
Same problem. Reply #12 solved it for me. Thanks.
-
Hi, whilst using https://www.fundingsecure.com (a financial site in the UK) I have found the same thing over the last 2 weeks or so. After 5 or 6 clicks in the site, 'Connecting...' and unable to log in again for a couple of hours.
Disabling the firewall whilst 'Connecting' allows the site to function again.
For the moment, disabling the port scan (thanks) seems to work- but needs more extensive experience to be sure.
Meanwhile I had rung their IT people- who had no such reports.
-
Hi, whilst using https://www.fundingsecure.com (a financial site in the UK) I have found the same thing over the last 2 weeks or so. After 5 or 6 clicks in the site, 'Connecting...' and unable to log in again for a couple of hours.
Disabling the firewall whilst 'Connecting' allows the site to function again.
For the moment, disabling the port scan (thanks) seems to work- but needs more extensive experience to be sure.
Meanwhile I had rung their IT people- who had no such reports.
Confirmed. Clicking link above gets me to the site but going anywhere else causes a block (time-out). IP is 185.64.90.244
-
This issue has caused problems for me on 2 different systems...
Laptop connected by ethernet, Kodi streams a video from my NAS for about a minute then hangs.
Works fine on WiFi though?
Desktop PC admin access to router on 192.168.1.1 works for 20 seconds then hangs.
Eventually after seeing this thread I discovered that switching the firewall off cures both these problems.
Examining the firewall rules log shows both problems are being caused by port scan blocking.
Enabling the firewall and disabling the port scans cures both problems.
So there is an issue with port scanning.
What other consequences are there for disabling port scans?
As an aside I also noticed I can't set the Clear log older than to anything other than 1 week; bug?
-
After disabling port scanning a couple days ago, the blocking of my NAS and some websites seems to have subsided, though I cannot say it is the right speed etc. without some more testing, which I don't have time for right now.
The 'rules' logs do show that before I turned off port scanning, the NAS was scanning and being blocked (image named withPS), and the other image is the list of the latest rules.
That said, I'm still getting multiple entries per minute numbers of entries in the 'blocked' logs, and it shows no rule, and also links to no application most of the time. I have tried editing it to allow 'all / all' and then deleting the rule (that the system says is not a rule) but still no change. I changed the setting 'if there is no rule, then...' to 'allow' instead of 'auto-decide' and the log still runs, but the 'no rule' entry in the rules column is blank. But the 'show application' still goes to nothing in the app manager.
The uncertainty of what is going on and the lack of control is what is getting to me now.
-
I have been using Avast for about 2 years now and haven't had any issues connecting to the internet or my router until about 9 PM tonight. I'm glad I came here... "disabling port scanning" :o did the trick. Thank you!
-
Hi All, same symptoms as everyone else; can't connect to NAS nor even router IP. Turned off port scan, no luck. Finally did full removal of AIS and reinstall. Then turned off port scan. That seemed to work finally.
Avast needs to fix this. I've got 6 licenses and been a customer for over 3 years. Now I've got to uninstall/reinstall on 5 other computers to fix a problem Avast created? Not good.
-
Here's a reply just received from Avast on this issue:
(http://screencast-o-matic.com/screenshots/u/Lh/1492611316235-25580.png)
-
I have struggled with this issue for a week, access to my NAS has and all internal resources have been blocked. I replaced the router with an old 100 Meg router and everything worked, logical assumption was that it was that the original router that had a problem. I then replaced the original router with a shiny new router, and shazam connectivity failed within a short period of time, I have pulled my hair out and tonight I came across an anomaly, I couldn't access any internal network items or any internet sites except believe it or not Facebook. It struck me that the Avast firewall could be an issue. Turned it off and the world came back, plus my internal network.
The old router I tried as part of the fault elimination had an internal address range of 192.168.20.x. If I hadn't turned the firewall off that was my next replacement item...
-
Note: Micro Update fixing Websites blocked by Firewall Port scan detection has just been released for AVAST. You can get this update immediately by rebooting and waiting ~ 5 minutes, otherwise it will arrive automatically in 12 hours (max).
-
Note: Micro Update fixing Websites blocked by Firewall Port scan detection has just been released for AVAST. You can get this update immediately by rebooting and waiting ~ 5 minutes, otherwise it will arrive automatically in 12 hours (max).
Thanks, but no change for me after updating. Avast Firewall still cryptically blocking the same safe sites after a couple minutes of browsing.
-
Did you restart your Computer after updating?
DJBone
-
Yes I did. But since you asked that, I restarted the machine a second time, and the problem may have resolved. Possibly the first reboot only initiated the update, and the second reboot finished the install of the fix. Either way, the URL's in question are now browsing with dramatically less latency, and no firewall blocking so far.
Will post here again later if these results prove short-lived.
-
Possibly the first reboot only initiated the update, and the second reboot finished the install of the fix.
yes , it's like this , after update we could see in UI (update tab) -> you need to restart your computer to finalize the installation or upgrade
-
Possibly the first reboot only initiated the update, and the second reboot finished the install of the fix.
yes , it's like this , after update we could see in UI (update tab) -> you need to restart your computer to finalize the installation or upgrade
Reboot is required it said. Did so and all is well.
-
I have the same issue with Warema Webcontrol and Linn Kazoo Client.
I tried updating by clicking the update button. Yes I rebooted too but the problem is still the same. What should be the program version after updating? My version is 17.3.2291 (build 17.3.3443.0) released on 30.03.2017 12:59:59.
-
Reboot again.
First reboot is needed to get the update, second one to finish the installation of it.
-
Reboot again.
First reboot is needed to get the update, second one to finish the installation of it.
Thanks Eddy but still the versions and the problem are the same.
-
You could try the latest beta: https://forum.avast.com/index.php?board=15
-
Just back from being away for a couple of weeks, and found Avast was preventing access to my Synology NAS. Tried the recommended solutions above (eg repair avast; disable port blocking etc) and no luck (I presume I was doing this after Avast applied the micro-update).
After a lot of trial and error, I can connect to the NAS is I set "Allow DNS" to "disabled" in the Packet Rules/System Rules - after that, it all works fine. However....I then can't connect to any other website as the DNS lookup doesn't work (and have to reset "Allow DNS" to "enabled" to browse the web).
Not sure what to try next on this?
oktup
-
You could try the latest beta: https://forum.avast.com/index.php?board=15
-
Try to get it to update, manually check for updates, restart and check again. And disable port scanning. Some of the features came back, and are gone again, like being able to tell Avast to allow all local traffic. So now I see mine says allow all applications that don't have a rule. Whatever.
-
I'm on program version v17.4.2294 in the meantime but still no improvement.
-
I'm on program version v17.4.2294 in the meantime but still no improvement.
Are you running avast free?
-
I'm on program version v17.4.2294 in the meantime but still no improvement.
Are you running avast free?
Yes
-
Did you perform a clean installation of avast ?
-
I'm on program version v17.4.2294 in the meantime but still no improvement.
Are you running avast free?
Yes
The free version of Avast doesn't have a firewall.
Clean Install of Avast:
https://goo.gl/4Ptzkf