What I can't understand is the firewall error bit (windows security center) of your original post. I can't see a) why it would be disabled and b) why it would stop the web shield and mail shield starting and c) why that would stop avast connecting. There are times when we might even suggest disabling a firewall (for a test) and see if avast can connect, so I don't believe that because a firewall is disabled that would stop avast's web shield starting or connecting.
However, if at the web shield isn't running I don't know if the connections would still be routed through the web shield proxy it would probably not connect.
What is your OS ?
What is your firewall, I suspect the windows firewall but I would like to confirm (as some firewalls if not fully started block outbound connections) ?
I assume that your connection is broadband and I'm wondering if the avast auto update check might also be running at the time, so I will suggest delaying that check, see ~~~ below.
~~~
- In avast5 you need to edit (using
notepad)
avast5.ini the
[InetWD] section of the C:\Documents and Settings\All Users\Application Data\Alwil Software\Avast5\avast5.ini (Windows 2000, Windows XP)
- Broadband connections, add this line:
AlwaysConnectedWaitSeconds=120 and
AssumeAlwaysConnected=1 if not present (or edit AssumeAlwaysConnected=0 to AssumeAlwaysConnected=1)
[InetWD]
AssumeAlwaysConnected=1
AlwaysConnectedWaitSeconds=120
When complete save the changes, avast's self-defence module will ask for confirmation, etc. answer Yes.
The figure is seconds and the above equates to two minutes, you could try that and adjust upwards if required, 180, 240, etc.
