This flaw is more annoying than debilitating, but is should be corrected by AVAST. The so-called "attacks" were merely the 5 PC's on my network coming on and off of the network at different times of the day. I then used Angry IP Scanner to identify and correlate the MAC addresses with IPv.4 addresses, which allowed me to identify the sources of the "attacks". From the Network Neighbors table, I was able to identify the MAC addresses of the IPv6 addresses recorded by AVAST. The Network Neighbors table is like an IPv4 ARP cache but for IPv.6.
AVAST FOR MAC FALSE POSITIVES PRO
What I did to understand what was going on was to download a demo copy of Net Scan Tools Pro and look at the Network Neighbors table. I did tell you that it was unlikely that I was receiving an attack from the outside since all the PC's on the network had Remote Desktop turned off. I've never dealt with IPv6 addresses so I could not identify the origin and tell you whether the IP addresses were internal in my network or from the outside. All the IP Addresses were in IPv6 and not IPv4. The notifications appeared to be in waves with some being blocked and others allowed, but always a connection attempt going in bursts of seconds, then ceasing after a while, then resuming again. Just after an October AVAST update, I started getting second by second notifications from the Remote Access Shield feature that a BruteForce attack was being made. Here's a short recap of what we were discussing. This is for AVAST Program Version (build.
I SOLVED the issue, and yes, AVAST is at fault for providing false positives with its latest update.
0 kommentar(er)
