Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: ultra1983 on September 22, 2007, 04:30:20 PM

Title: Conflict with Comodo Personal Firewall 3
Post by: ultra1983 on September 22, 2007, 04:30:20 PM
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.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: warlock on September 22, 2007, 05:02:40 PM
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.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: DavidR on September 22, 2007, 05:09:24 PM
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 (http://www.avast.com/files/tutorials/ws_ieproxy.htm)
For IE - dialup users - Tutorial - Web Shield Proxy Set-up for IE (Dial-up) (http://www.avast.com/files/tutorials/ws_ieproxy_dialup.htm)
For Firefox users - Tutorial - Web Shield Proxy Set-up for Firefox (http://www.avast.com/files/tutorials/ws_ffproxy.htm)

I don't know if you would also have to remove the port 80 redirect from the Web Shield, Customize, see image.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: ultra1983 on September 22, 2007, 06:37:08 PM
My OS is Win XP Pro SP2.

I already tryed to cancel the redirection, but I think avst can't protect the system without...
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: DavidR on September 22, 2007, 06:46:59 PM
It can by manually configuring the browsers to us it, have you tried that ?
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: ultra1983 on September 22, 2007, 08:59:16 PM
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...
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: Lisandro on September 22, 2007, 09:28:36 PM
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.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: ultra1983 on September 23, 2007, 10:01:32 AM
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...
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: cvsa on September 23, 2007, 10:18:18 AM
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 ::)
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: DavidR on September 23, 2007, 02:09:12 PM
Unfortunately that link is off-limits to guests, etc.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: cvsa on September 23, 2007, 04:57:00 PM
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..
 8)
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."
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: DavidR on September 23, 2007, 05:07:17 PM
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.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: Lisandro on September 25, 2007, 02:49:54 PM
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. ???
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: warlock on September 25, 2007, 06:31:03 PM
... 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 ...
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: warlock on September 28, 2007, 09:13:54 PM
Good news, Comodo Firewall 3 beta 3 (3.0.9.229) fixed this problem.
Title: Re: Conflict with Comodo Personal Firewall 3
Post by: lukor on October 02, 2007, 04:58:04 PM
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


Hi guys, I am happy to hear Comodo team fixed that in the newest version. But anyway I wanted to inform you that this trick means: "disable WebShield".
Very strange how firewall gurus on the Comodo forum can operate with terms like TCP port without thinking.

If you want to call your Mom via telephone no one would suggest calling a different number if your mother is currently not at home. This is the same.

So again:
Unless you do a lot browsing on port 12020 (which I doubt anyone here have ever used for anything), this settings disables WebShield for you. The number 80 means HTTP. HTTP servers provide their pages on TCP port 80 if they want to be accessible by others. Similarly POP3 scanner uses 110, which is the TCP port number where POP3 service is usually offered. Changing ports to some obscure values does not make any sense.






Title: Re: Conflict with Comodo Personal Firewall 3
Post by: gdiloren on October 02, 2007, 05:06:57 PM
Just to let you know I have non conflict with Comodo 3 beta. Just leave it in learning mode and don,t touch anything. Only conflict (is it related?) is with spyware terminator that I can't open withouth trying 2 or three times upon and error message of windows that there is no disk. I use Vista. :)