Avast-computer can't connect to the Internet - Avast-computer can't connect to the Internet - enart.xn--w1yw3putk.com

ENART.XN--W1YW3PUTK.COM
welcome to my space

Avast-computer can't connect to the Internet

Avast-computer can't connect to the Internet
Published by: wktd 2010-03-12

• Your Operating System version:
Windows 2000 SP4
• Outpost version:
6.0.2284.253.0485
• What plugins are installed and actively running:
Whatever the defaults are.
• How you are connecting to the Internet:
Rogers High Speed Cable – Linksys Router

Can’t connect to the Internet. It appears that the basic Internet connection is there. I must admit that I installed Outpost first followed by Avast. Before installing Avast I was able to connect to the Internet without any problems.

I can testify that installing Avast! AFTER installation of Outpost will result in no internet connection. Reinstall Outpost and it will detect Avast! and it tells you what you have to do to co-exist. But, I'll be nice and tell you what it says.

To avoid conflicts during product operation, please set the "Start" value in the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServic esaswTdi key to 4 and restart your computer. This will disable Avast! TDI Shield.

It works.

Lukas welocme to the forum

Thank you for your input. As this is a user run forum I'm not sure anybody will be able to give you sufficient details to satisfy you as a developer. However, I'll make Agnitum aware that you are here so that they can contact you.

That's a good idea Robb. Now that there are so many compatability issues it would be nice to have a stand alone program to check this issues or at least list them. Suggest it to them.

Did any of those experiencing this problem check the OP Options, Applications and ensure that the ashWebSv.exe (the avast Web Shield) wasn't Blocked as that would also block internet connection to http pages.

Actually, the solution above, the change to the Registry, is to totally disable the Web Shield. (See post #3 (http://outpostfirewall.com/forum/showpost.php?p=166509&postcount=3) The Web Shield is what is incompatible with Outpost, basically because it is having 2 "firewalls" running at the same time; which is a no no. So even if you make rules allowing avast! Web Shield, eventually what happened for me is you basically have no internet connection until you disable one or the other and reboot. I think that is basically what cdplayer and I found. And apparently what Agnitum found. It is the driver "aswTdi" that causes the problem and it must be disabled.

Also the following actions get taken by the compatability wizard during install when avast! is found:

Action=wl_hook_exclusion ashserv.exe
Action=sandbox_exclusion ashserv.exe
Action=wl_hook_exclusion ashwebsv.exe
Action=sandbox_exclusion ashwebsv.exe
Action=wl_hook_exclusion ashmaisv.exe
Action=sandbox_exclusion ashmaisv.exe

Are you saying that you made rules for ashwebsv.exe and now don't have any problems with both running??? I'm just very curious.

P.S. All of this applies to version 6 of Outpost. I just noticed that you are running version 4 DavidR.

If you install Outpost after Avast! (or any other AV), Outpost Install will tell you exactly what I did.
Hey Rah,

Maybe this gem of information can be placed in a FAQ? :)
Could that work?
Elton

There should be a sticky about this Avast error http://forum.gamert.nl/images/smilies/icon_wink.gif
I agree with you SuicideCow! There is something to be said about the order in which these software packages should be installed. :)

Glad I could help.

Thanks Manny. I'm wondering if all of the "gems" contained in compatability.ini are so important to people? Compatability.ini is, after all, basically a database of rule-sets for installation. I think what hurts so bad is that it is only checked at installation time. The performance hit would be too great to have it checked all the time. What might be nice would be for Agnitum to take the "check" piece of code and make it a stand-alone utility that could be run at any time to check for new compatability issues one might have introduced...???

Anyway, thanks for stickying it, and I keep and eye out for issues resolved by compatability.ini.

Ok, I changed the title to include Avast and made the thread a sticky.
Thanks Manny! :cool:

There should be a sticky about this Avast error http://forum.gamert.nl/images/smilies/icon_wink.gif

Solution 1.

JUST don't install NETWORK Shield when installling Avast! antivirus

Tested on Avast 4.8.x (mine is b1169) + Outpost Firewall Pro ver. 6.0.2279.251.0482

There should be a sticky about this Avast error http://forum.gamert.nl/images/smilies/icon_wink.gif

If you install Outpost after Avast! (or any other AV), Outpost Install will tell you exactly what I did.

Uninstalling Network Shield is not a permanent solution, since Avast fixes it during program updates. I like both Avast and Outpost. I just bought a new license of Avast for 3 years, and still have 2 years license of Outpost. I hope these two products can co-exist! Thank you.

The Web Shield (ashWebSv.exe) is not a firewall but a localhost proxy to scan http content for viruses, etc. it redirects port 80 traffic to local port 12080 and is a very valuable resource. There is no avast! TDI Shield as you have said it is a driver not an avast shield/provider which can be configured by the user.

I'm in no rush to update to OP Firewall Pro 2008, even though I have a lifetime license and it would cost me nothing to upgrade. This is just one of the reasons.

I would have thought that Agnitum would have contacted Alwil software at avast.com, etc. about this supposed conflict to resolve any issue than simply have OP 2008 users completely disable what is 'not' a firewall but a localhost proxy.

The Network Shield I believe also uses the aswtdi driver and that cold loosely be termed a firewall but it is more like intrusion detection only monitoring the common entry ports for worms/viruses/exploits, etc. It is most certainly not a full firewall.

I would have to ask why this is a problem for OP 2008 and not the many other firewalls that are being used by avast users on the avast forums (Comodo, Online Armor, PC Tools, etc. etc.).

The web shield is effectively doing nothing than a few other AVs that also have http port 80 monitoring.

I submitted a suggestion. You know, they already call it the "Compatability Wizard" in problem tracking..... hmmmm :)

Solution 1.

JUST don't install NETWORK Shield when installling Avast! antivirus

Tested on Avast 4.8.x (mine is b1169) + Outpost Firewall Pro ver. 6.0.2279.251.0482

Sure, that's what I meant by uninstalling Network Shield -- if avast is already installed.

I believe it should be a permanent solution based on what Lukor said. If you uninstall the Network Shield (or did a custom install without it), Windows Add Remove Programs, avast Antivirus, Change/Remove, select Change and uncheck the Network Shield and OK your way out, then you should be fine.

If you do a program update it should respect that the providers which you don't install 'shouldn't' suddenly be installed on the program update. The new files for the provider should be there, but not installed.

So should you choose to enable it at another time then the updated files are there and you reverse the above exercise.

Communication between the two companies would be a fine thing, leading to a resolution and co-existence. However Agnitum should have at least tried to contact Alwil to explain why the problem is there rather than simply have users hack around in the registry to disable an element of another program. This with the introduction of self-defence in version 4.8 would also make that hacking harder without first disabling the self-defence.

As Lukor said the update would reverse any registry hack, but not if you had uninstalled the Network Shield as he suggested until this is resolved, but that will require Agnitum contacting Alwil to say why there is a conflict, perhaps then will there be a proper solution.

Hello cdplayer,

Does this Agnitum's kb article (http://www.agnitum.com/support/kb/article.php?id=1000030&lang=en) help?

Hi,

what is the reason that Outpost does not work with this particular TDI filter? (the avast! Network Shield).

As a avast! developer I know the implementation details of the aswtdi.sys filter and I am not aware of any suspicious non-compatible tricks inside the driver.

This TDI filter in question has no connection with the WebShield HTTP scanner and does not provide any support for this process.

Can anyone help me to understand this issue? Or is there any more proper way to address the developers?

BTW: better that editing the registry, if Outpost Firewall 2008 is really incapable of running with our TDI filter, I would suggest uninstalling the component (Network Shield) altogether. The registry entry for the Network Shield gets automatically fixed during avast! program update checks, so if it is really needed it would not work as a permanent solution.

Thanks,
Lukas.

I installed Avast! and Outpost Firewall Pro ver. 4.0.1007.7323 (591) took it in its stride. The combination works very well. I have done this with both Windows 2000 SP4 and Windows XP SP2/3. Is this a problem with OP 6 only?

Network Shield is on.

Ok, I changed the title to include Avast and made the thread a sticky.