Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: se2mobile on April 08, 2008, 11:17:11 AM
-
hi,
this is my first time posting to this forum.
Before updating to avast 4.8, iAVS update using avast version 4.7 was just ok behind proxy.
But after updating to avast 4.8, iAVS update always failed.
It said that the proxy needs authentication.
I've tried every proxy setting in avast, but with no avail.
right now i have to download the update file from avast website to keep avast up to date.
Any help would be appreciated ;D
-
I have this problem too.
I cannot update base and the program through proxy server in new Home version 4.8.
There is an error "Cannot connect to server ".
Change a settings of a proxy server from "Auto detect" to special does not help.
If I return to version 4.7, the base update becomes possible again.
Probably, a problem is not in a proxy.
Help please
AndrewP
-
try to repair avast by going add/remove>click avast>scroll down>repair
-
If the proxy is corrected set (type, address and port; user and password) it should work... What happens if you click on 'Test' button?
-
I already uninstalled and re-installed avast 4.8 and try different settings of the proxy settings, but still with no avail.
-
Please reply to the specific question that Tech asked you.
-
when the 'test connection' button was clicked, the following message was shown:
"Cannot connect to server using these settings. Please change the proxy settings and try to test again."
-
I am sorry ... what is the setting you used for this check?
-
proxy server setting -> auto detect (use IE settings)
proxy server setting -> Specify proxy server -> Type: HTTP; address; x.x.x.x; port: 8080
Authentication : Basic or NTLM
Tks for reply ;D
-
I got the same problem.
I'm behind ISA proxy server with NTLM auth.
-
I am having the same exact issue. I was fine until I did an auto-update to 4.8 and now the auto-update feature doe snot work at all. I have my proxy settings set up and previous versions used to be just fine.
09.04.2008 20:59:56 general: Started: 09.04.2008, 20:59:56
09.04.2008 20:59:56 general: Running setup_av_pro-491 (1169)
09.04.2008 20:59:56 system: Operating system: Windows2003 ver 5.2, build 3790, sp 2.0 [Service Pack 2] AMD64
09.04.2008 20:59:56 system: Memory: 23% load. Phys:3211208/4192936K free, Page:4194303/4194303K free, Virt:2042392/2097024K free
09.04.2008 20:59:56 system: Computer WinName: CASSICKR
09.04.2008 20:59:56 system: Windows Net User: ENTERPROCITY\rcassick
09.04.2008 20:59:56 general: Cmdline: /downloadpkgs /noreboot /updatevps /silent /progress
09.04.2008 20:59:56 general: DldSrc set to inet
09.04.2008 20:59:56 general: Operation set to INST_OP_UPDATE_GET_PACKAGES
09.04.2008 20:59:56 general: Old version: 44a (1098)
09.04.2008 20:59:56 system: Using temp: C:\DOCUME~1\RCASSI~1.ENT\LOCALS~1\Temp\_av_proI.tm~a01604 (287269M free)
09.04.2008 20:59:56 general: SGW32P::CheckIfInstalled set m_bAlreadyInstalled to 1
09.04.2008 20:59:56 internet: SYNCER: Agent=Syncer/4.80 (av_pro-1169;p)
09.04.2008 20:59:56 system: Computer DnsName: cassickr.Enterprocity.local
09.04.2008 20:59:56 system: Computer Ip Addr: 10.0.0.51
09.04.2008 20:59:56 system: Installed in: C:\Program Files\Alwil Software\Avast4 (287269M free)
09.04.2008 20:59:56 internet: SYNCER: Proxy enter01:8080
09.04.2008 20:59:56 internet: SYNCER: Type: standard HTTP proxy (rfc2616,2617)
09.04.2008 20:59:56 internet: SYNCER: Auth: no authentication
09.04.2008 20:59:56 package: Part prg_av_pro-491 is installed
09.04.2008 20:59:56 package: Part vps-8032900 is installed
09.04.2008 20:59:56 package: Part news-4b is installed
09.04.2008 20:59:56 package: Part setup_av_pro-491 is installed
09.04.2008 20:59:56 package: Part jrog-33 is installed
09.04.2008 20:59:56 general: Old version: 44a (1098)
09.04.2008 20:59:56 file: SetExistingFilesBitmap: 1054->144->55
09.04.2008 20:59:56 general: GUID: 053be840-bf61-48aa-ad23-a4094e27f094
09.04.2008 20:59:57 general: Server definition(s) loaded for 'main': 180 (maintenance:0)
09.04.2008 20:59:57 general: SelectCurrent: selected server 'Download924 AVAST Server' from 'main'
09.04.2008 20:59:57 package: GetPackages - set proxy for inet
09.04.2008 20:59:57 internet: SYNCER: Proxy enter01:8080
09.04.2008 20:59:57 internet: SYNCER: Type: standard HTTP proxy (rfc2616,2617)
09.04.2008 20:59:57 internet: SYNCER: Auth: no authentication
09.04.2008 20:59:57 internet: SYNCER: Proxy l/p: enterprocity\administrator/***
09.04.2008 20:59:57 general: Entered SetupProcessPro::Do( INST_OP_UPDATE_GET_PACKAGES )
09.04.2008 20:59:57 general: Entered SetupProcessWin32Avast::Do( INST_OP_UPDATE_GET_PACKAGES )
09.04.2008 20:59:57 general: Entered SetupProcessWin32::Do( INST_OP_UPDATE_GET_PACKAGES )
09.04.2008 20:59:57 general: Entered SetupProcess::Do( INST_OP_UPDATE_GET_PACKAGES )
09.04.2008 20:59:57 general: progress thread start
09.04.2008 20:59:57 internet: SYNCER: Agent=Syncer/4.80 (av_pro-1169;f)
09.04.2008 20:59:57 internet: Using NTLM
09.04.2008 20:59:57 internet: INTERNET_PER_CONN_AUTODISCOVERY_FLAGS=5
09.04.2008 20:59:57 internet: INTERNET_PER_CONN_FLAGS=15
09.04.2008 20:59:57 internet: ERROR:HttpGetWininet, catch returned 0x00002F00
09.04.2008 20:59:57 internet: Using NTLM
09.04.2008 20:59:57 internet: INTERNET_PER_CONN_AUTODISCOVERY_FLAGS=5
09.04.2008 20:59:57 internet: INTERNET_PER_CONN_FLAGS=15
09.04.2008 20:59:57 internet: ERROR:HttpGetWininet, catch returned 0x00002F00
09.04.2008 20:59:57 general: InvalidateCurrent: invalidated server 'Download924 AVAST Server' from 'main'
09.04.2008 20:59:57 general: SelectCurrent: selected server 'Download93 AVAST Server' from 'main'
09.04.2008 20:59:57 package: GetPackages - set proxy for inet
09.04.2008 20:59:57 internet: SYNCER: Proxy enter01:8080
09.04.2008 20:59:57 internet: SYNCER: Type: standard HTTP proxy (rfc2616,2617)
09.04.2008 20:59:57 internet: SYNCER: Auth: no authentication
09.04.2008 20:59:57 internet: SYNCER: Proxy l/p: enterprocity\administrator/***
09.04.2008 20:59:57 internet: while trying to get file 'servers.def.vpu', error 0x20000004 has occured, try 1
. . .
09.04.2008 21:00:30 internet: while trying to get file 'servers.def', error 0x20000004 has occured, try 9
09.04.2008 21:00:32 internet: Using NTLM
09.04.2008 21:00:32 internet: INTERNET_PER_CONN_AUTODISCOVERY_FLAGS=5
09.04.2008 21:00:32 internet: INTERNET_PER_CONN_FLAGS=15
09.04.2008 21:00:32 internet: ERROR:HttpGetWininet, catch returned 0x00002F00
09.04.2008 21:00:32 general: InvalidateCurrent: invalidated server 'Download208 AVAST Server' from 'main'
09.04.2008 21:00:32 general: SelectCurrent: selected server 'Download507 AVAST Server' from 'main'
09.04.2008 21:00:32 package: GetPackages - set proxy for inet
09.04.2008 21:00:32 internet: SYNCER: Proxy enter01:8080
09.04.2008 21:00:32 internet: SYNCER: Type: standard HTTP proxy (rfc2616,2617)
09.04.2008 21:00:32 internet: SYNCER: Auth: no authentication
09.04.2008 21:00:32 internet: SYNCER: Proxy l/p: enterprocity\administrator/***
09.04.2008 21:00:32 internet: while trying to get file 'servers.def', error 0x20000004 has occured, try 10
09.04.2008 21:00:34 internet: tried 10 servers to get file 'servers.def', but failed (0x20000004)
09.04.2008 21:00:34 file: GetNewerStampedFile:GetFileWithRetry failed: C:\DOCUME~1\RCASSI~1.ENT\LOCALS~1\Temp\_av_proI.tm~a01604\onefile, servers.def, error: 0x20000004
09.04.2008 21:00:34 package: Tried to download servers.def but failed with error 0x20000004.
09.04.2008 21:00:34 general: Err:Cannot connect to download208.avast.com (75.126.203.66:80)
-
When you click the test button, does it work?
Which firewall are you using?
-
No, the test connection fails saying that it cannot connect to the server.
I am behind an ISA firewall and running the firewall client.
Nothing has changed in my setup other then my recent auto-update to the 4.8 version. The older versions ran in this exact same configuration just fine.
-
I got the same problem.
-
Yeah, apparently I am not the only one. My mother-in-law is also having the same issue and so is someone from work.
I hope we hear something on this soon.
-
Can you try if the latest beta version solves this?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it or go here (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
-
Nope, sorry. Same error.
It also threw that error (cannot connect to www2.avast.com) during the installation of the beta.
-
I am behind an ISA firewall and running the firewall client.
Seems a firewall block...
-
Little too much of this for me to believe this is always a firewall block. I will be very happy to be proved wrong.
However I cannot suggest any diagnostics that come to mind to test with - but I hate leaving folks in this predicament.
Clutching at straws - have all of the options available in the avast Program Settings > Update Connections > Proxy been tested.
-
Yeah, I went through all the settings int he test area and none of them worked. Normally I would think this was a firewall block too but I have literally changed nothing anywhere in the last 6 months. It's been 3 months since the firewall was rebooted, maybe I will try that and see if it fixes things, but I never had to do any custom rules for Avast to work before so nothing should need to be set now. I also run with the XP firewall turned off.
-
Just seems really odd that even though I have Avast set up for my proxy server and to use NTLM authentication (and I have a good domain\user and password setup) I am seeing this in the log:
11.04.2008 02:15:30 internet: SYNCER: Proxy enter01:8080
11.04.2008 02:15:30 internet: SYNCER: Type: standard HTTP proxy (rfc2616,2617)
11.04.2008 02:15:30 internet: SYNCER: Auth: no authentication
11.04.2008 02:15:30 internet: SYNCER: Proxy l/p: enterprocity\administrator/***
Also, when I sniff using Wireshark the HTTP GET results in a 407 (proxy requires authentication).
Kind of looks to me like the connection is being made using no authentication
-
Greetings!
After updating the program up to version 4.8 I have received the same problem. Version 4.7 works normally.
For the Internet I use MS ISA Proxy with authorization.
Excuse for my English :)
-
Interesting results...
As a lst ditch effort last night I rebooted my firewall server and no joy.. still had the problem...
To try to determine if this was a firewall issue (even though all the sniffing I was doing did not indicate it was) I did this:
1) Changed my NIC default gateway to use a gateway address that bypasses the ISA firewall. I have a secondary egress router that routs around things for a few devices that I have that I can't get to go through the ISA server (IE: Playstation, TiVO, etc..)
2) Disabled the ISA firewall client.
3) Ran a connection test and is PASSED!
OK, so then I started to think this was my firewall all of a sudden. I was able to run an update and get Avast to update all it files. I then rebooted.
I figured that if I had to do this once in a while I could live with it. I put my setting back tot he way they were and just for a heck of it I ran another test. It FAILED! :( I went to bed feeling beat...
This morning I woke up and checked the windows event log before coming into work. It updated on its own at roughly 6am this morning!
I am going to run a few more tests when I get home today but so far this looks promising.
-
i'm having this problem too. trying to update at office behind ms isa proxy and it failed. before updating to 4.8 it's update just fine.
edit: sorry.. my connection just sucks :'(
-
i'm
I'm too ;)
-
After checking + modify ZoneAlarm settings with no avail, I tried to uninstall it and install Comodo Firewall Pro (free edition).
Then I tried to check Avast update manually... with SUCCESS ;D
I still don't know why Avast could not update with ZoneAlarm installed and behind proxy (I already deleted all the programs on ZA program lists except some windows services that were not recommended to be deleted by ZA).
It could be the Windows services that were not deleted from the ZA program lists but it could be something else.
But, I am glad that I can check update behind proxy again 8)
-
The same problem.
It doesn't depend on type of proxy or firewall.
It doesn't depend on type of authentication.
Agree with rcassickKind of looks to me like the connection is being made using no authentication
Wireshark confirms that.
-
What's new with this problem?
when avast 4.8 will correctly complate authentication ?
-
Beta version build 1178 still had bug in NTLM authentication, but is fixed in latest beta build 1187.
Since you probably cannot update program, here is link for english setup:
avast! Home
http://public.avast.com/~forejt/1187/setupeng.exe
avast! Professional
http://public.avast.com/~forejt/1187/setupengpro.exe
Uninstall previous version, restart and install this beta version. Then in proxy settings for updates fill proxy server address and port, and set NTLM authentication.
If you'll need setup for another language, just let me know.
-
Beta version build 1178 still had bug in NTLM authentication, but is fixed in latest beta build 1187.
Thanks a lot! It works!
-
I will try it latter today when I get back home.