My Firewall (Sygate Pro, Latest patches, etc) keeps asking permission for access from Avast.setup to access several different remotes IP’s (Avast servers I presume). When I select yes, it comes back and asks the same question, but for a different IP.
Is there a problem with the update servers, or something elses. This has only happened since the Avast update, dated 27/02/04
Thanks
Clive
avast.setup changes with every program update. That is, its MD5 checksum changes as well… You need to tell the firewall that you don’t want to check the MD5 of this file, or at least update the stored MD5 hash to the one of the latest version.
For info about the IP addresses, please refer to the FAQ: http://www.avast.com/i_kat_81.html#idt_1366 Now I see we have a new server download5.avast.com which is not yet in the FAQ --we’ll need to update this asap…
Thanks
Vlk
Yeah, I’m having the exact same problem with my Sygate (free version) as well. I have avast.setup set as “allowed”, yet Sygate still keeps asking if avast.setup is allowed to connect. Very frustrating, because I like Avast and Sygate very much.
I have avast.setup set as "allowed", yet Sygate still keeps asking if avast.setup is allowed to connect.
Doesn’t this phrase contain a contradiction (or doesn’t it imply there’s a bug in Sygate?).
Anyway, as I said, the avast.setup file does change so it’s possible that Sygate is in fact complaining because of this. I’m sure there’s a way to tell sygate that this specific file CAN change.
Thanks
Vlk
Exactly.
trundles off to dig through Sysgate documentation
BTW thanks for the agitation: http://pub116.ezboard.com/fcompuforumfrm17.showMessage?topicID=688.topic 
You’re welcome. I believe in spreading the word about good programs.
(Your link needs the “.topic” part at the end added in).
http://pub116.ezboard.com/fcompuforumfrm17.showMessage?topicID=688.topic
In regards to the server update problem,
I couldn’t see any options for configuring the MD5 hash checking. There is an option for “Enable dll authentication” which I have unchecked (I tried it and got annoyed at the never-ending queries). Perhaps the free edition is much more limited than the pro.
I could set up an advanced rule and jam all the IPs into the “trusted IPs” box, but that’s such work. 
So, I removed avast.setup from the list of Sygate Applications, and then performed a manual Avast Update, and checked the box for always allow. Hopefully I fixed it. It will take a day or so to tell, because the manual updates seem to go thru fine, it’s the automatic background checks that seem to trigger this problem.
So much for that hope.
http://www.babster.com/smilies/ohwell.gif
Right after I posted that, it started again.
I must have checked the “Remember My Answer” box and said yes to (literally) 19-20 popup boxes for “avast.setup.exe is trying to connect…” like below
http://www.babster.com/gifs/avast-sygate1.gif
Finally Avast brought a pop-up window which stated:
Information about current update: Last encountered error: Server download1.avast.com (66.98.166.72:80) is down.Total time: 4:30
A follow-up manual program update check works fine.
The only difference between manual and auto updates is that in the former case, avast.setup is spawned directly by the application from which you invoked the update. In the auto-update case, however, avast.setup is executed by ashServ.exe, the avast service. The service runs under the LocalSystem account, i.e. not under the account you’re currently loggen on.
This changed in the latest build. In the previous versions, all avast.setup’s were being executed by aswUpdSv.exe - the ‘avast iAVS4 Control Service’. In build 357, this service lost much of its importance and is used only when invoking manual updates from non-administrative accounts…
Vlk
If the user don’t have a non-administrative account, could the service be disabled?
Could the user make a link for the service and put it into Startup Menu of that non-administrative account?
If the user don't have a non-administrative account, could the service be disabled?
I guess so… (this has always been true, though - this didn’t change in the last version).
Could the user make a link for the service and put it into Startup Menu of that non-administrative account?
No. The point with services is that you can’t manage them (start/stop etc) unless you’re an admin! ;D
avast.setup is executed by ashServ.exe, the avast service
Yeah, I noticed that. I forgot to mention it, but ashServ.exe is also set to “Allow”.
The problem is that Sygate pops up a window for each and every IP that the update goes to, I guess.
Edit: I see that this is being experienced by all Sygate users.
Specs: Windows 2000 Pro (admin rights), Sygate Personal Firewall 5.5 build 2525.
Hi,
:-[ Experiencing the same problems and it’s pissing me off to always allow Avast about 18 to 20 times on each update.
I never had this before, so really something changed. Before this happened, I only had to acknowledge the change after the update and that’s all.
I’m logged on as administrator and using Windows XP Pro.
Worth investigating why we’ve to allow Sygate to update and why it fails on every update. Manual works!
I am having the exact same thing with Sygate. If I remove it from my list and let the new version come up when it’s 4 hours to check and I select to allow it to connect and check box to not ask every time what does checksum have to do with it? It would be detecting it like I just installed Avast for the 1st time? Thanks. What is the fix anyone?
??? It’s getting worse. Eveytime I reboot, Avast updates although my VPS is up-to-date.
This is the log I get:
That’s already three times today I had to push 20 times to allow, but the update fails. Further more there isn’t an update, so what’s going on?
Can someone explain this code?
As strange as it may seem, today there was an update.
VPS 0402-5 was installed without the above problems.
I don’t know what was going on, but I’m glad that I don’t have to allow Avast 20x or more to update.
Was there a change in the update to correct this behaviour from Sygate?
No change. Maybe Sygate took a day off on Sunday… 8)
As you can see it’s a Sygate trouble…
Why don’t you disable Sygate for a while, update avast! and try to troubleshoot with updated avast! running? :-\
Mine is still doing it. 
The only solution right now is to set Sygate to “Allow All” (which kinda defeats the purpose of the firewall).
I don’t mean to agitate, but this behavior was not happening prior to the .357 update.
The error in the Warning Log which seems to pertain to the failed updates is
29.02.2004 18:57:31 NT AUTHORITY\SYSTEM 628 Function setifaceUpdatePackages() has failed. Return code is 0x20000004, dwRes is 20000004
Is there a way to go back to the version prior to .357?
Technical wrote: As you can see it's a Sygate trouble...??? That's silly to put the blame on Sygate, without proof.
Babster wrote: Mine is still doing it. I don't mean to agitate, but this behavior was not happening prior to the .357 updateSo it seems! ::) I don't know why mine isn't doing it anymore! This behavior started with the update prior to the one you mentionned.
I’ll have to wait until the next update to see what happens.
;D I’ll keep you posted.