In this case I'd advise to find the responsible application and configure it correctly or disable it. It is also possible that an application is trying to access shared folders (e.g., a video player trying to load shared videos/songs) without correct credentials, but it's impossible for the shield to know. The PC originating the connections could be infected with malware trying to self propagate, or be part of a botnet launching a brute force attack. When multiple consecutive authentication attempts from a single IP fail, the Remote Access Shield classifies this as suspicious behavior. Even if the originating computer is in your local network - local SMB is a common vector for spreading malware from a computer to the rest of the network (as explained for example here: ). As stated in the other threads, we realize that non-malicious connections can be blocked if they appear suspicious. I'm sorry you are having this issue and I'll do my best to resolve it. ![]() I hereby publicly accept the issue at hand. ![]() I've read every related thread in this forum, no real answers to be found and no Avast solutions at all.īesides all of the above, and as I described in detail in my initial post, why exactly is it that I am able to use "block all connections" and use the exception list to allow/whitelist IPv4 addresses but it will not work on IPv6 addresses, how about Avast providing an answer to that if nothing else, hi there Jakub, maybe you have something to say about this specific issue, as I said, I 100% identified the address being blocked as another PC in my local network, I need real answers with real solution, as it is, Avast has become unusable garbage software, sorry to say. Hi rocksteady, Like every other thread here, there are no answers to the real issue, this all started with the new Remote Access Shield, it is 100% at fault for the problems many of us are seeing, Avast will not publicly accept the issue at hand, hopefully they are working to fix it even without acknowledging the problem. Any way this can be fixed? Right now the only way I'm able to connect from one PC to another is by disabling Samba Protection, which defeats the purpose of it's existence. I can report that the exception list works for me when using an IPv4 address (192.1.168.xxx), but doesn't work with IPv6 addresses like the one above (fe80::5801:7d88:xxxx:xxxx). Besides, the IP will change so even if it worked with the exceptions I would have to add new ones every time the IP changes, which makes no sense, why did it just start doing this and how can I fix without losing protection to my PC? But it still blocks it, the only way I can unblock is by un-ticking "Enable Samba protection". I tried to unblock by ticking the "Block all connections except the following" and added the URL address above, fe80::5801:7d88:xxxx:xxxx. ![]() The URL is a PC in my local network and never before was blocked like this. I am getting alerts for Incoming connection blocked and I am trying to figure out why this is happening all of a sudden.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |