Automatic Updates Errors...

[inquisitive]

Hello people:

I'd like to have your opinion as to why avast! pro (most recent) is unable to process automatic updates.  When it tries to download the updates, it comes up with the read and yellow error message box stating:
'Information about current update:
Last encountered error: Cannot connect to download921.avast.com (74.86.125.42:80).'
I run WinXP Pro in an office LAN environment.  I don't know which settings should be tweaked to allow the program to receive automatic updates without getting the error messages.  Thanks in advance.

Inquisitive

[Lisandro]

Please, post the last 200-250 lines of avast log: C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log

[DavidR]

Last encountered error: Cannot connect to download921.avast.com (74.86.125.42:80).'

This error can/may indicate your firewall blocking.

What is your firewall ?
Does it allow avast.setup internet access ?
- If it does delete the entry for it and do a manual update, this will force the firewall to ask permission again. 

[inquisitive]

Please, post the last 200-250 lines of avast log: C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log

I attached a plain-text file that contains the info. 

[psw]

Probably reason is that you are using direct connection to Inet method
28.04.2008   18:22:18.000   1209378138   internet   SYNCER: Type: no proxy
28.04.2008   18:22:18.000   1209378138   internet   SYNCER: Auth: no authentication
and getting WSAETIMEDOUT error (10060 = 0x274C).
Ordinary method for Inet access in office LAN environment is via some proxy. So at least you should select correct method of avast! Inet access.

[inquisitive]

Hello helpful readers:

It appears that the proxy server settings were not valid (not entered ).  It's worth noting that avast! av has never given me problems in the past with regards to automatic updates.  This is the first time that I have been working with it in a LAN environment.  It works fine now.  Thanks to all that offered their help. 

Inquisitive

[Lisandro]

Just the infamous 0x20000004 error... difficult to troubleshoot. I'm surprised you've found the proxy was the error so soon. Thanks for coming with that psw

I also recommend trying to update to the latest beta.