Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by judson

  1. Your disks appear to be about 90% full: that can slow anything (as used space increases, performance of everything decreases). You mention your 'server PC': please explain what that means. You also mention OA's HIPS: does performance improve if the HIPS is disabled?
  2. Cannot edit the above - just clarifying my post. I upgraded to OA 5.1 - manually rather than automatically - several days ago. Since then, each time that I have attempted an update (of signatures?), I have received the above errors/messages. When I enabled automatic updates, OA updated (signatures?) without any errors/messages.
  3. I am seeing the same and getting a pop-up 'a2wl.dat is corrupted' - manual updating - over several days - Win XP, OA Premium. As a 'test', I switched to automatic updates and did not have the same problem - OA/signatures updated. The issue may be with manual updates. I am using OA 5.1: manual upgrade from v5.0.
  4. My post was not about UAC. It was about W7. The OP requested advice about behaviour of OA compared with the behaviour of the W7 firewall (W7 x64). Your reply may well be correct if UAC is disabled. However, UAC is enabled by default, and the W7 firewall is configurable (inbound and outbound control). I can assure you that UAC does more than just "alert you when a process requires administrative privileges".
  5. Is that correct for W7 (firewall) - in particular W7 x64 - with UAC at its default setting?
  6. If you have 'intercept loopback interface' enabled/checked (which is recommended), you should allow connections to localhost (which is your PC) for any trusted program - don't block, as you state at your post #1. Many programs use localhost loopback. As long as the Program in these requests is one that you trust, you should allow them.
  7. Yeah I understand about drivers/XP/W7/x86/x64, et seq; that is not the issue. It just seems as though I am not alone. However, thanks
  8. Please be careful about providing advice about W7 settings: they are different from those of XP. For example, what you have quoted can be dependent upon a number of other settings. I have no "network and sharing center" on my W7 PC; I have the relevant setting disabled. Furthermore, IE9 is different from IE8 (and earlier versions).
  9. Thanks - reply is appreciated. I tend to agree that the default settings are unlikely to cause issues.
  10. Will (paying) OA users ever be able, or allowed, to understand its ICMP settings?
  11. ... and it appears to result in issues such that reported by the OP. I can assure you that I observe the consequences on our XP PCs.
  12. Thanks, again. I assumed that XP does not experience the issue; but I had to ask. I remain uncertain about x86/x64, as there are insufficient examples (posts) to confirm that it is one, the other, or both. 'Always trust software ...' may indicate that it is unsigned or its certificate has expired. There may be other reasons, but security software should not prompt such alerts. I have not seen a (this) driver alert on my W7 x64 PC with UAC at default (maximum). I have installed drivers with this configuration. I have not installed OA on an x64 PC. It appears to be an OA issue (and should be explained in the OA help pages).
  13. Does the prompt occur for any/every install of OA? Is the prompt dependent upon the OA version (free/premium/++)? Is the prompt dependent upon the Windows version (XP/Vista/7, x86/x64)?
  14. For completeness, I never disable my A-V when doing MS Update. However, I am certain that the issue has nothing to do with my A-V. I don't regard it as a major problem, just an observation. I agree with Peter2150 that it has existed for a long time, but not forever.
  15. Thanks - perhaps this should be added to the OA help pages (Installing Online Armor).
  16. I have UAC set to 'Default'. Driver is the key word in my post.
  17. XP SP3, OA Premium, F-Prot A-V - my A-V will have no effect on this issue - nothing else of interest to this issue.
  18. I don't seem to be able to edit my posts! I should, therefore, explain. I use OA on two XP PCs: 'my ICMP settings' are for another product on XP and for the Windows 7 (x64) firewall (check its default ICMP settings).
  19. My ICMP settings (IPv4 and OS-independent - I block IPv6): Incoming - 0, 3, 8 (with remote address restricted to gateway), 11. Outgoing - types 0, 3, 8. I have plenty of logs (behind a router) to confirm that these are low-risk settings. Unfortunately, OA does not permit such settings.
  20. Reliable sources seem to agree that ICMP types (functions) 0,3,8,11 are all that should be allowed by a firewall; however the direction and source IP address are just as important in allowing/denying each of these types; Wilders has an excellent thread on same. I hope that explains why I started this thread. I think that OA allows all outgoing ICMP packets. I think that the check box refers to incoming packets - the checked types are allowed (incoming). The OA help page does not help. As for RAW protocol, I am unsure if allowing any protocol other than those allowed by firewall rules is wise. I think, for example, that allowing RAW allows IGMP. I agree that clarification would be welcome. BTW: If you ping an IP address, does OA create a rule? If so, I wonder how that affects the ICMP settings.
  21. Yes. I see same on our XP Pro PC. Interestingly, it does not occur on our XP Home PC (where learning mode remains enabled after restart).
  22. The ICMP tab (OA paid) lists a number of ICMP types under the heading 'Function'. Each type has an associated checkbox - 'Allowed'. The default, checked types/functions are not in accordance with recommended practices; they are rather strange. Does the checkbox relate to incoming and/or outgoing ICMP packets? If all checkboxes are cleared, does OA allow/block incoming/outgoing ICMP packets. Why were the default settings selected? Do they present an issue to the uninitiated user?
  23. Your replies are appreciated - thanks and understood.
  • Create New...