firewall blocked sfp from accessing web
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
-
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
Is that the free version? I can't vouch for the commercial one, but my opinion of the Sygate one after trying it out was that it was somewhat flaky.andrew wrote:
I've got sygate firewall
I now use a "proper" SPI/NAT Open Source (GPL) combination running on my router (a lot of routers use GPL licenced software ... sometimes without declaring the licence!)
I'm fortunate in that our company uses Sophos AV software, which allows all its employees to install a "home" version. Sophos is IMO te best AV out there, but unfortunately, it's only licenced out to businesses, not to home users.
Unless the Sygate FW is confused, it does sound likely that your SFP.exe has been infected. If your AV software doesn't detect anything and you want to be absolutely sure, feel free to zip it up and send it to me and I'll check it with Sophos.
Royston
-
- Posts: 236
- Joined: Sun Jul 29, 2001 4:00 pm
- Location: Rotterdam, The Netherlands
okay -
just checked - it was indeed c:sfp\app\bin\sfp.exe that sygate reported trying to access the internet.
Whether this is sygate getting confused or not I'm not sure. I've done a virus scan with avg virus scanner (free edition) with the latest updates, and found no viri
I'll zip it and send it to Counterparts in Bath for detailed analysis.
Thanks guys!
Andrew
<font size=-1>[ This Message was edited by: andrew on 2004-12-08 14:48 ]</font>
just checked - it was indeed c:sfp\app\bin\sfp.exe that sygate reported trying to access the internet.
Whether this is sygate getting confused or not I'm not sure. I've done a virus scan with avg virus scanner (free edition) with the latest updates, and found no viri
I'll zip it and send it to Counterparts in Bath for detailed analysis.
Thanks guys!
Andrew

<font size=-1>[ This Message was edited by: andrew on 2004-12-08 14:48 ]</font>
-
- Posts: 236
- Joined: Sun Jul 29, 2001 4:00 pm
- Location: Rotterdam, The Netherlands
Hi Andrew,
I'm a user of Sygate Pro, and I can confirm that sometimes it gets confused and doesn't report the correct program name.
It doesn't happen a lot (once a week for me maybe?), but when it does the problem seems to disappear after a reboot.
It's quite annoying, but usually I'm reassured by the fact that the program is trying to access a site that I know about. For example most of the times some random program is reported as attempting to contact the McAfee site, and I know it's actually just the mcafee daemon trying to check for an update..
Voila!
Camed
I'm a user of Sygate Pro, and I can confirm that sometimes it gets confused and doesn't report the correct program name.
It doesn't happen a lot (once a week for me maybe?), but when it does the problem seems to disappear after a reboot.
It's quite annoying, but usually I'm reassured by the fact that the program is trying to access a site that I know about. For example most of the times some random program is reported as attempting to contact the McAfee site, and I know it's actually just the mcafee daemon trying to check for an update..
Voila!
Camed
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
Oddness, I didn't see it, but it could be that my rather harsh Spam Assassin settings clobbered it! Quite likely...
Was the attachment zipped up by the way? I know that .exe attachments will get blocked before they reach me.
If you put "SFP" in the subject line, and try again, I'll filter it into a folder where I'll spot it
Royston
Was the attachment zipped up by the way? I know that .exe attachments will get blocked before they reach me.
If you put "SFP" in the subject line, and try again, I'll filter it into a folder where I'll spot it

Royston
Had the same issue some time ago, go here to see the responses I got back then, he says shamelessly adverting his own threads
.
Issue persisted but was not a showstopper, and just as I changed from Symantec to Norman, I got a hunch that SFP tried to reach an internal port in my own PC. Norman does not seem to be responsing to this phenomenon, but that might as well be some configuration issue ?
Anyone ?
Stubbe

Issue persisted but was not a showstopper, and just as I changed from Symantec to Norman, I got a hunch that SFP tried to reach an internal port in my own PC. Norman does not seem to be responsing to this phenomenon, but that might as well be some configuration issue ?
Anyone ?
Stubbe