I just got notified today of an update to the software and I let the machine do this automatically. Then, I rebooted as was necessary and allowed my Sygate PRO firewall access the internet - - - over and over again. The firewall asks if I want to allow the connection, I tick the box to ‘always allow and never ask again’, and then continue. The requests keep appearing and, of course, it’s quite annoying. >:(
This never happened with any previous version of the software. Has anybody else with Sygate experienced this?
I had another program that caused difficulty after updating; someone else had the same problem and, for them, they removed the checkmark next to ‘anti-application hijacking’. However, of course, for more security I would surely like to have that activated. I did not test to see if the problem disappears when that security choice isn’t checked.
It’s not a ‘good’ thing, but I’m glad to know that it just wasn’t me. Hopefully, this problem will be fixed since it affects the regular Sygate version too (as you mentioned).
Also, I did test & disabled the ‘anti-application hijacking’ and the constant requests do not appear. I don’t know if this option is only available in the PRO version.
Have you tried removing all the Avast applications from Sygates trusted applications and then telling Sygate to allow Avast again when it prompts you? I can’t remember which firewall I was using at the time but I remember that removing the applications from the firewall and letting it detect it again solved the problem.
somehow I think the update server isn,t working when Sygate pings it and therefore it keeps on trying so hence the repeating box asking for connection.I,ve emailed support but no reply as yet. It works on manual ok,so Ithink there must be a different server for the automatic updates.
Kerio is free; the download allows you to use the full version for 30 days, but then it will revert to the slightly limited free version. . .but I’ll stick with Sygate.
Have you tried removing all the Avast applications from Sygates trusted applications and then telling Sygate to allow Avast again when it prompts you?
Yes, I’ve tried that multiple times. However, now later in the day, the problem seems to be gone and the
‘anti-application hijacking’ option is back on. I do think there was something temporarily wrong with the update server.
Mine is doing the same thing…This happened after the last program update as well??? Is it the servers or isn’t it? Last time it cleared up on it’s own after about 2 days after program update. Can’t be Sygate if it clears up on it’s own. Again Avast people…Is it your server? Thanks.
Had the same problem after updating to 4.1.389 and was going completely crazy. Nothing seemed to work until I realized that Sygate wasn’t requesting to update the Avast program after going from 4.1.357 to the new one. I tried removing the Avast programs from Sygate’s applications but that didn’t work. I simply uninstalled and reinstalled Avast with the new setup file and wallah! All is well.
I tried to uninstall the program and reinstall and it seemed to go ok (although the ‘add or remove’ didn’t work). I installed the program to a different location; it seems to work when I click on the icon on the screen - - but, after a bootup, there’s no spinning ball or the other ball at the bottom of the screen. In addition, a window of a directory always appears for some reason.
I guess I’ll try some registry cleaners and maybe see if I can find an older version of the software. Hopefully, I won’t have to go for another virus program.
Get the feeling all the problems are with Sygate and not Avast since it’s their inability to pick up the program update. Anybody check out their forum?
Your problem lies in Sygate not Avast. For some reason, something in the update confuses Sygate and it will not “see” or truly “recognize” Avast as the program wishing connecton and therefore does not match it to a “permission” which you have given it.
Reinstalling Sygate corrects the problem.
Why does reinstalling Avast work then? Well, when you reinstall Avast, it gives Sygate another chance to “recognize” the program which it usually does.
A type of corruption occurs within Sygate causing the Problem. I have only had this happen ONCE in my use of Avast in my Win98 machine, and never with my WinME or WinXP using Pro.
It is just one of those things that happens lacking a more technical explanation.
