Conflict with Comodo Personal Firewall 3

[ultra1983]

Good morning.

I'm using Avast Home Free with the latest Comodo Personal Firewall 3 version.

This version encounters a problem working with avast antivirus.

There's something wrong in the avast port rediraction management. Avast redirects port 80 with its web server, but cfp 3 brakes this redirection, so that http protocol doesn't work. To browse the internet I have to disable avast's port redirection leaving the web protection's port redirection field blank.

Does Avast Web Protection works fine with this modify? Is it still able to protect my computer?


Is there any way to solve this problem?


Really many thanks.

[warlock]

With your current settings WebShield isn't protecting your system anymore. As there is no way to get the automatic redirection working with Comodo (in XP, it seems its working in Vista, at least for most people), you will have to manually set WebShield proxy in your browser and other programs you want to protect. The way you set it depends on the program you are configuring, but the correct settings are Proxy adress: 127.0.0.1, Port: 12080.

[DavidR]

What is your OS ?

The web shield redirects port 80 to its proxy, 12080 this enables avast to scan http content using this localhost proxy before it is saved to your browser cache.

Does it allow ashWebSv.exe internet access ?
- If it does delete the entry for it and reconnect to the internet, this will force the firewall to ask permission again.

This doesn't seem to be a problem in the regular 2.4 release and I believe this may already have been discussed in the forums. So a forum search for comodo version 3 may return some information, but I think that they had to go back to the regular 2.4. version.

As for trying the manual setting of the browsers to use the web shield proxy (may be different for IE7):
For IE - broadband users: - Tutorial - Web Shield Proxy Set-up for IE
For IE - dialup users - Tutorial - Web Shield Proxy Set-up for IE (Dial-up)
For Firefox users - Tutorial - Web Shield Proxy Set-up for Firefox

I don't know if you would also have to remove the port 80 redirect from the Web Shield, Customize, see image.

[ultra1983]

My OS is Win XP Pro SP2.

I already tryed to cancel the redirection, but I think avst can't protect the system without...

[DavidR]

It can by manually configuring the browsers to us it, have you tried that ?

[ultra1983]

Yes, but now firefox is very slow and some contents that don't follow browser's proxy settings aren't available.

Moreover this kind of configuration can't be used where there's really a proxy server...

[Lisandro]

Moreover this kind of configuration can't be used where there's really a proxy server...

Yes it can. Otherwise, the local proxy IS a proxy server.

[ultra1983]

Moreover this kind of configuration can't be used where there's really a proxy server...

Yes it can. Otherwise, the local proxy IS a proxy server.

If I set avast's proxy in the browser, in case of phisical proxy, I have to set it in avast's proxy configuration, but be sure that the largest part of advanced contents like streaming or web application won't be available because embedded players aren't sometimes able to follow proxies.

Moreover now firefox is very very slow...

[cvsa]

read that, maybe it helps....

http://forums.comodo.com/cfp_beta_corner/cfp_and_avast_web_sheild_ashwebsvexe_resolved-t11435.0.html

otherwise, wait for final version of comodo firewall 3

[DavidR]

Unfortunately that link is off-limits to guests, etc.

[cvsa]

ok here's what they say : "everything works fine by just changing from Web Shield options http forwarding or something from port 80 to port 12020

I have learned that using Avast that I had to set 127.0.0.1:12080 proxy to ALL these to work correctly:

-Firefox
-IE
-Thunderbird
-WinAmp
-Last.Fm

I dont know whats going on..
 
Whats going on is that CFP somehow breaks redirection of HTTP traffic, that Avast WebShield normally does. Strange is, that redirection of POP3/SMTP/IMAP/NNTP traffic (done by another process of Avast) works fine."

[DavidR]

Thanks for the update, I would have thought that removing the 80 rather than replace it with a non-http port number would have been the better option. If the port 80 redirect isn't there than avast won't redirect but the manual setting of the browsers to use the avast web shield proxy should still work.

[Lisandro]

Whats going on is that CFP somehow breaks redirection of HTTP traffic, that Avast WebShield normally does. Strange is, that redirection of POP3/SMTP/IMAP/NNTP traffic (done by another process of Avast) works fine."

I'm not that sure of this... the redirection seems to be working in my two-weeks period test of Comodo beta 3 and Vista.

[warlock]

... As there is no way to get the automatic redirection working with Comodo (in XP, it seems its working in Vista, at least for most people), you will have to manually set WebShield proxy ...

[warlock]

Good news, Comodo Firewall 3 beta 3 (3.0.9.229) fixed this problem.