Hi there, here’s hoping someone can answer my query. I’ve been using Avast Premium for a while now with Vista Home Premium. I know Vista is no longer supported but I haven’t had any issues till now so I’m hoping it’s just an error that can be corrected and not a sign that i can no longer use Avast with my computer.
3 weeks ago Avast flagged up a Network threat, my router was shown as “Your device is working okay” but highlighted red and when looking at the error it mentions that there is a fake DNS on my device sending me to sites that might not be who they say they are. The 2 addresses mentioned are:
Since then I have been through ipconfig and checked everything and flushed the dns cache, checked the Hosts file which is default, setup a static ip with 8.8.8.8 and 8.8.4.4 as the primary and secondary DNS’s, installed and re-installed the newest version of Avast and been sent a new up-to-date router by BT, a Home hub 4 and I’m still getting the same error. Anyone have any ideas? :-\
Inel Core 2 quad, Vista HP sp 2 up-to-date, 4gb, 160gb etc.
P.S. I’m also getting a another error that happened around the same time. Every time i do a Smart Scan it gets to 67% and then Malwarebytes flags an Outbound ip called popcash.net but this probably isn’t related as there are no outbound rules in the firewall and when doing a full scan with Mbam it finds nothing.
P.S. I'm also getting a another error that happened around the same time. Every time i do a Smart Scan it gets to 67% and then Malwarebytes flags an Outbound ip called popcash.net but this probably isn't related as there are no outbound rules in the firewall and when doing a full scan with Mbam it finds nothing.
Hi there, and thanks for replying. I understand Popcash.net is related to some sort of virus but I have been unable to find any traces of it in the computer. I have scanned it with ever virus/malware and adware program known to man and none of them find anything wrong. The only time I get a red flag is when Avast is scanning. Once it reaches exactly 67%, Malwarebytes flags an outbound rule. But when you search for this rule, it doesn’t exist. Would there be a reason why Avast doesn’t find it or is it something Avast is triggering while scanning?
I’ve also checked the router with the program you suggested, and as I said I had it replaced with a new 1. But I’m also still receiving the DNS error while using the Avast network scanner. But BOTH routers couldn’t be affected, unless Avast is flagging 1 of the servers BT uses by accident. Anyone else have a thought about this? Any help would be appreciated! Cheers.
