SPF Problem

From: Ian Pollard (m0flc_at_yahoo.co.uk)
Date: 03/19/05


Date: Sat, 19 Mar 2005 21:52:27 +0000

I have tried to use Sygate Personal Firewall Version 5.6 and the latest
Sygate Personal Firewall Pro V 5.5. If I try to use either version of
this firewall, I get an error report that tells me SPF has encountered a
problem and needs to close. If I use an earlier version, it works OK
apart from leaving a port open, I think it is port 135. I can only
close that port manually if I use the pro version but that leads me back
to where I started, it doesn't work on my machine. I am running Windows
XP HE Sp2 with I GB of memory and approx 180 GB HD with usage at about
20GB. I have AVG pro anti virus. Any ideas??

Ian

-- 
Ian Pollard//Wooler//Northumberland//UK
                 m0flc@yahoo.co.uk


Relevant Pages

  • Re: Sygate Personal Firewall open port 1025
    ... > I'm running Sygate Personal Firewall 5.6 Free on Windows XP Pro. ... > I run the shield's up test from www.grc.com and it says my port 1025 is ...
    (comp.security.firewalls)
  • Sygate Personal Firewall open port 1025
    ... I'm running Sygate Personal Firewall 5.6 Free on Windows XP Pro. ... I run the shield's up test from www.grc.com and it says my port 1025 is ...
    (comp.security.firewalls)
  • Re: SPF Problem
    ... WinXP Pro SP2, 512mb, 120gb hd, AVG free edition. ... >I have tried to use Sygate Personal Firewall Version 5.6 and the latest ... > apart from leaving a port open, I think it is port 135. ...
    (comp.security.firewalls)
  • Re: ZoneAlarm more trouble then its worth?
    ... and failed miserably at ad blocking especially when ad blocking was ... OTOH Sygate Pro 5 (even when coupled with AdSubtract for ad blocking ... At that page is also a link for the Sygate Personal firewall v5 beta ...
    (comp.security.firewalls)
  • cant access files from local network
    ... >no one can access my files from the network. ... >have absolutely no prob at all accessing their files. ... >(sygate personal firewall) to make sure that it wasn't ... >pro at xp pro so i'm sure it's something small and stupid ...
    (microsoft.public.windowsxp.security_admin)