Avast seems to be blocking incoming connections to Apache Web Server

[aajax]

I occasionally do some testing that utilizes an Apache Web Server.  This might be the first time on a Win7 computer that is running Avast Free Antivirus (AFA).  After spending a good bit of time verifying that Windows Firewall was configured properly I decided to experiment by starting that Win7 computer without AFA.  Apache worked fine after making that fairly simple change.  I think the AFA setup is showing that whatever firewall feature might be available is not present.  Can someone explain this finding?

I'd also point out that I wasn't able to find what I'd call an intended way to turn off (shutdown, stop, etc.) AFA.  Is that just showing my ignorance or is that intended?  I think this is an example of a very normal situation where such would be desired.  All manner of other troubleshooting would seem to also create this need.  It ended up requiring what I'd call an unnatural technique.  What does Avast suggest for accomplishing such?

[Asyn]

Provide details...

[.: Mac :.]

Hi Aajax!

First, you can disable the product by right-clicking the tray icon and choosing to disable the shields under Avast Shields control - for example disabling until next reboot.

Avast Free does not have a firewall component per say, but it does include web traffic scanning. As Asyn mentions you will need to provide more details about the Apache issue for us to be of much assistance.

Cheers,
Mac

[aajax]

The problem of course is lack of details.  Does it help if I add that when trying to access a website from another computer the browsers (Firefox, Chrome, and IE) all come back and say they cannot establish a connection with the designated server.  When the target computer that is hosting Apache is booted up without Avast running (i.e., no other change) everything works as expected.

[.: Mac :.]

Have you done any experimentation with exclusions? Perhaps exclude the Apache processes?