|
TWbrkzzk1 -> RE: ZoneAlarm (9/28/2004 1:30:31)
|
quote:
ORIGINAL: bobby
Try not allowing "process216" access and see what happens... you can always give it back permission if you need it.
I'm used to seeing references like that in kernel messages, but never as an application that needs access to the network...
I tried Google and came up short.
Do you run anything like spybot or Adaware to trash spyware? I'd run every scan you can think of just to be sure, or until somebody can explain what that one means.
Plus, it's good to run those kind of scans weekly just to be safe... along with things like Antivirus updates and such.
As far as the intrusions, that can be misleading. It could be your ISP pinging your modem or any number of things...
I have over 10,000 blocked intrusions since I installed the last ZA update and almost 28,000 blocked access attempts.
That may sound high, but when I used Norton Firewall it was rediculously higher. I would get 3,000 of them a day. I was really paranoid until I started asking around.
(Still am, but I feel much better after the medication)
The majority of them turned out to be from Comcast (Then AT&T) reaching out to touch my broadband modem.
It's also possible that it's blocking one of those fun random-IP attacking virus monsters that float around out there unprotected... without a firewall you can catch one just for connecting.
[:D]
quote:
Try not allowing "process216" access and see what happens... you can always give it back permission if you need it.
I'm used to seeing references like that in kernel messages, but never as an application that needs access to the network...
I tried Google and came up short.
Do you run anything like spybot or Adaware to trash spyware?
The file name for process 216 is fftlyby.exe. It is located in C:\winnit\system32\fftlyby.exe.
The destination IP it was trying to connect to is 64.105.132.250:53
The destination DNS is lsanca54-pub-ns1.covad.net.
I do have Adaware and I ran it earlier today.
|
|
|
|
