![]() You shouldn't have to make any changes when using a VPN as I understand it, as having the VPN configured in your network adapter (which is how you connect to a VPN) should route all connections/traffic through the VPN automatically. You could run a trace to check for this, but again, it's not very likely so I'd recommend checking AVG's firewall settings before doing anything else to try to correct it. Another possibility would be a problem on your ISP's end where their routing servers are failing to connect to Malwarebytes' update servers. Another would be if you use a proxy to connect to the internet but haven't entered the proxy credentials into Malwarebytes' settings, but such configurations aren't too common, especially for home users so it isn't too likely. One example would be entries in your HOSTS file blocking some or all of Malwarebytes' servers, but unless you're infected by malware that modified your HOSTS file or you deliberately added Malwarebytes entries to your HOSTS file, such entries should not exist. There are other possible causes, but they are far less common. ![]() Since you're using AVG IS which has its own firewall rather than the default/built-in Windows Firewall, it's likely just a matter of excluding/allowing Malwarebytes to connect to the internet in AVG's firewall settings. The most likely culprit would probably be your firewall.
0 Comments
Leave a Reply. |