Cannot connect to update server

Running Firefox 8.0.1; Win7 Pro x64. Issue persists with or without firewall/malware programs running. I have made no changes to my OS

Suddenly Avast 6.0.1289 will not update either definitions or program. I have program set to manual, pop-up alerts re update, click to update, update window opens and, after several minutes, both the definitions and program update boxes read “cannot connect to server a759sl.avast.com (208.43.153.10:80). Total time 8:08.”

Also, if I right-click the Avast icon and click on update, both the engine and virus definitions and program options are grayed out.

Maybe you can set avast to use no proxy at all (and not automatic detection).
Please, upload (attach) the avast log:
C:\ProgramData\AVAST Software\Avast\log\Setup.log
or C:\Program Files\Alwil Software\Avast5\Setup\setup.log

If the file is too big for the forum, post the last 400-500 lines of it.

To cut it down its size, I zipped (AvastLog.rar) the setup.log file. Since *.rar is not an allowed file type, I changed the extention to .TXT (AvastLog.txt). You already know this but . . . to open, select “open with” from the context menu and choose your favorite archive program - or - change the extension to .rar

Thanks for your assistance.

Monk

When you change the file extension and upload, the archive always got corrupt.
The upload process the file differently.
Please, post back the last lines as I’ve said before.

Odd! I have no problem DLing and opening the file.

Attached is a redacted setup.log which includes only 11/29/2011 update attempt(s), one of which includes failed settings tweaks.

It appears that suddenly many people are having trouble with updates and yet suggestions urge that the issue lies within users’ systems - logically, an unlikely scenario.

Albeit free, I must, nevertheless, rely on an AV app that is reliable - which Avast is proving to be anything but.

Going to give the free Outpost suite a try; mods feel free to mark this thread closed as I will not be checking back.

I appreciate the opportunity to have used Avast for these several years as well as the attempts by those who have contributed in search of a resolution.

Monk