Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: c53204 on February 28, 2004, 10:08:43 AM
-
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 (http://pub116.ezboard.com/fcompuforumfrm17.showMessage?topicID=688.topic)
In regards to the server update problem,
1. This wasn't happening before.
2. I ~did~ allow access when the Sygate box popped up stating that the signature of the avast.setup file had changed (after the update to v. 4.1.357)
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. :P
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.
??? (http://www.babster.com/smilies/headscratch.gif)
-
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
-
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...
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.
- Using Avast Pro 4.1.357 - VPS 0402-4
- Sygate Personal Pro 5.5 build 2525
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:
- 28.02.2004 11:51:10 1932 Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002.
- 28.02.2004 12:06:38 460 Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002.
- 28.02.2004 22:53:29 232 Function setifaceUpdatePackages() has failed. Return code is 0x00000002, dwRes is 00000002.
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 update
So 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.
-
Technical wrote: As you can see it's a Sygate trouble...
??? That's silly to put the blame on Sygate, without proof.
No, it's not. I'm using a firewall right now (ZA free) and nothing happens with the 357 build of avast!
I used with Sygate and Kerio and everything was right in the past...
Some avast! users have Sygate firewall, ask them for proof. ;D
-
Technical wrote: No, it's not. I'm using a firewall right now (ZA free) and nothing happens with the 357 build of avast!
I used with Sygate and Kerio and everything was right in the past...
Some avast! users have Sygate firewall, ask them for proof.
??? Well, know-it-all, explain me why my Sygate didn't ask again to allow for the new update VPS 0402-6? And now VPS 0402-7 without the problems above! ;D
::) I only hope the other users don't have these problems again!
-
Strange, i have latest avast! 4 pro and my VPS was not updated even after i got email (new VPS info) and after the avast! page was updated. Than i ran manual iAVS and than i recieved update.
Shouldn't PUSH update it as soon as VPS is released?
Or is PUSH system iniciated after mail,updated page and manual download?
-
VPS 0402-6 was updated through the Push, but the next wasn't.
??? Even the VPS-update didn't work, only the program update did the job.
Why?
-
Definitely something fishy going on there... :-\
Temporarily disabling Sygate is something you'd like to avoid, right? ;)
-
Hi Vlk,
Definitely something fishy going on there...
Temporarily disabling Sygate is something you'd like to avoid, right?
I really like being protected by Sygate & Avast, so disabling Sygate is not an option.
??? It's strange that it all started by a previous VPS!
:o I'm not putting the blame on Sygate, nor on Avast, but I definitely want to know what's causing this behaviour to almost all Sygate users? Not like Technical, who immediately jumps to conclusions.
::) I'll see if I can find something in the logs and eventually post it here.
;D I'm really glad of not pushing 20 times anymore to allow the update.
;) Eric
-
??? Well, know-it-all, explain me why my Sygate didn't ask again to allow for the new update VPS 0402-6? And now VPS 0402-7 without the problems above! ;D
I apologize for what make you think I'm a know-it-all. I'm not.
Sorry if you think that. I'm here trying to learn and help as a lot of other users can tell you :)
Sometimes, take a conclusion could be the short way to solve a 'loop' problem. As a lot of other users are not experiencing trouble with avast! update that make me think (not blame, I'm not here to blame nothing and no one) that is was a firewall problem.
At least, you can see I have some experience trying to help the others in this forum and can recognize some problems by their sympthoms.
Again, sorry if this is not what you think about my behavior.
-
Technical wrote:I apologize for what make you think I'm a know-it-all. I'm not.
:) Apologies accepted!
At least, you can see I have some experience trying to help the others in this forum and can recognize some problems by their sympthoms.
I know you've some experience, because I'm also visiting this forum from time to time to learn and help others whenever I can.
Maybe you can shed some light on this: Send a test e-mail and the VPS is not the same as in the about.
??? How come?
(http://users.pandora.be/eborght/Elwyn/avast.jpg)
;) Thanks for looking into this.
-
Maybe you can shed some light on this: Send a test e-mail and the VPS is not the same as in the about.
??? How come?
;) Thanks for looking into this.
Right now: my email note is: Virus Database 0402-6, 03/01/2004.
The About dialog says: 0402-7
Really strange the behavior of the variable %VPS% of the notes ::)
-
Most likely a minor bug in the 'notes'. This is a new feature (prior to v. 357, it only reported VPS date, not exact version) so it is possible that the mail plugins are querying this info only once a day or something...
That will be quite easy to resolve I guess...
-
BTW I've just heard that yesterday, there was a small problem resulting in the fact that the PUSH e-mail was actually sent before the files were uploaded to the servers, so that may explain the second problem.
Sorry for this
Vlk
-
I removed Sygate Personal Firewall and changed to ZoneAlarm for now.
-
guys, sorry this bug ;-( vps version is read only when avMaiSrv is started, so if updated during avMaiSrv session there is no change of this number. It's bug in Internet Mail Provider. It will be fixed in next version; sorry ;-( pavels
-
Hey no problem :) I waited half hour for new update,for Norton i'd have to wait 2 days ;)
-
pavels wrote: guys, sorry this bug ;-( vps version is read only when avMaiSrv is started, so if updated during avMaiSrv session there is no change of this number. It's bug in Internet Mail Provider. It will be fixed in next version; sorry ;-(
:) Thanks for letting us know pavels & Vlk!
Do you mean the update after VPS 0402-8? ::) Updated to 0402-8, but mail still shows 0402-7!
Babster wrote: I removed Sygate Personal Firewall and changed to ZoneAlarm for now.
:-\ Sorry, you had to change the firewall. Problems concerning Sygate appear to be fixed, because it's not requesting to allow anymore for me. ::) Maybe it's also fixed for the others?
??? What was the cause? Really don't have a clue about this behaviour of Sygate.
-
Sorry, you had to change the firewall. Problems concerning Sygate appear to be fixed, because it's not requesting to allow anymore for me. ::) Maybe it's also fixed for the others?
??? What was the cause? Really don't have a clue about this behaviour of Sygate.
I have no idea. My Sygate was ~still~ popping up all the 20 or some windows asking for permission to connect, even though I had carefully gone thru one of the episodes, checking the box and saying "Yes" to each and every one of them. And all of the various Avast! programs were set to "allow".
I do like my firewall; it was easier to just switch for now. Maybe if I reinstalled Sygate again it would work? I don't have the inclination right now.
We'd have to hear back from c53204 (the original author of this post - who never ~did~ reply again), uffbros, and any other Sygate users.
The title of the thread should really be "SYGATE and Server access errors" to be descriptive.
-
For me avast! Pro and Sygate Pro work like charm :)
You need to check Use this settings always (or something like that) when you apply new rule for application. avast! asked me only once for both update components.
-
For me avast! Pro and Sygate Pro work like charm :)
You need to check Use this settings always (or something like that) when you apply new rule for application. avast! asked me only once for both update components.
::) We did apply the Always setting, but to no avail. Sygate kept asking for allowance & the update always failed.
Didn't you experience the same problems?
Babster wrote: We'd have to hear back from c53204 (the original author of this post - who never ~did~ reply again), uffbros, and any other Sygate users.
The title of the thread should really be "SYGATE and Server access errors" to be descriptive.
Sure would be helpful if they were to report their experience with the previous & new updates.
;) I completely agree on changing the description of this thread.
-
Hm,check Tools\Applications...
and add Allow to all avast! components if there is Ask command.
Its strange that update fails even if you allow it... :-\
-
Hm,check Tools\Applications...
and add Allow to all avast! components if there is Ask command.
Its strange that update fails even if you allow it... :-\
::) We all did that! Didn't change anything.
-
Why do you always have to use rolleyes smiley?
-
Why do you always have to use rolleyes smiley?
Because I don't have a clue what was causing this, also your suggestions for allowing Sygate. We already knew this and did it. Nothing helped. :-\
Further more I like to add smileys, it changes the reading and gives some meaning.
My only point is that you didn't experience these problems, if I'm correct. A majority of us had/have these problems.
Maybe it's solved, but I really would want some info from other users of what they are experiencing right now with the new updates.
;) Eric
-
Hey i can't see what you have and what you don't have done. I try to help. Guess you know already know everything...
-
Hey i can't see what you have and what you don't have done. I try to help. Guess you know already know everything...
;) No offence intended. I know you're trying to help.
And no, I don't know everything, but I'm still looking for clues.
I'm no beginner on this field and I'm sure many others know to a certain degree how to use this firewall, including configuration.
:-[ Sorry, for not making that statement sooner.
You too are a Sygate user and you didn't experience this?
Are there others who didn't have these problems?
Maybe it's a wild goose chase. ;D
So until I or others find clues, we are unable detect the cause.
;) Bye for now, Eric
-
i disable the auto update got sick and tire of it popup the firewall every feaking 20 time it like to connect update server, so i do it manuly update thru shortcut.
when it popup 20x its really get tire of it all. disable the auto update and check it when you first log-on to the internet you get no error from the firewall for the antivirus trying to update on its own.
disable the auto update for virus and programs do it on your own you find you get no error from the firewall do to the change that was done in the new update tool.
by the way after this i upgraded to Sygate personnel firewall pro Vr 5.5 build 2525 and still get them goofy enable it to connect so its not the firewall its the setting the new update did, sorry i don't care for the new setting were it bugs me like crazy, it stay disable auto/update i do it on my own.
-
You too are a Sygate user and you didn't experience this?
Are there others who didn't have these problems?
I'm using Sygate 5.5 free version along with the latest version of avast! with no problem. I have been using avast! for well over a year and recently installed Sygate around February 10th. (I don't know what bearing when I installed the programs has, but who knows.) So far no problems; Sygate asks permission only once or twice and only after a program, not VPS, update.
Jarron
98SE
-
i solved this problem with an advanced rule allowing the ..\Alwil Software\Avast4\Setup\avast.setup file to access everything
-
Me is using sygate, too. Allow avast (in your firewall options) so it will not ask all the time...should work than.
-
Allow avast (in your firewall options) so it will not ask all the time...should work then
*sigh*
-
Got two updates through Sygate with no problems. I'd try to reinstall it if i was you...
-
I have Sygate Pro and Avast! I have had no problems. The only time Sygate pops up is when the Avast! program changes. No problem getting virus updates at all.
There is a new version of Sygate Pro that I install a week or so ago. Maybe check to see if there is an updated free version too?
-
Hi,
:) Thanks for responding.
From what I've read I suppose only a minority among the Sygate users did experience this behaviour.
??? Strange
;) Eric
-
Hi there,
I'm using Sygate 5.5 in combination with avant! Home without any problem. I've copied my settings
Avast e-mail scanner service - Allow
Avast service GUI componet - Allow
\Program Files\Alwil Software\Avast4\Setup\avast.setup - Allow
I hope you can do something with it.
Suc6
-
I'm using Sygate 5.5 in combination with avant! Home without any problem. I've copied my settings. I hope you can do something with it.
:) Thanks for your settings, but unfortunately that's what we all did.
;D For now all new updates went through without problems, so I suppose it disappeared the same way as it came, in stealth. :-\
::) We may never find what caused this!
So until another Sygate user is still experiencing this strange behaviour, it remains an unsolved problem.
;) Eric
-
I switched from ZoneAlarm to Sygate Free edition latest version 2 days ago. Sygate asked me 2 times only for permission regarding avast! and it asked never again...Works just great !
Rejzor, thanks for advice.. it really takes up less system resources than ZoneAlarm... :)
Cheers !
-
From the Sygate forum http://forums.sygate.com/vb/showthread.php?s=6f9c1e59e86f688115f704529488fbd2&threadid=8910&highlight=avast (http://forums.sygate.com/vb/showthread.php?s=6f9c1e59e86f688115f704529488fbd2&threadid=8910&highlight=avast):
Try disabling Anti-Application Hijacking
I don't have Anti-Application Hijacking, maybe that's why I haven't had a problem. Do others with the problem have it?
Edit - Actually I just realized the anti-application hijacking is part of the options of Sygate, and not a separate program as I was thinking, and I do have it enabled. I still haven't had the problem, so I don't know.
-
I have it enabled too, but still I don't have any problems. Sygate works just great, it's so silent, I don't even know it exists in my PC... although, I have my GVC Gnet IP0010 hardware router/firewall, but still I feel much more comfortable to have one of those software firewalls enabled too...
Cheers !