G
Guest
This is a Defender question in a roundabout kind of way - but I'd never have
noticed it if I hadn't been focusing on Defender issues in the last couple of
weeks - so here goes.
Because I've been looking at Event Viewer frequently, I've noticed that
maybe 2 or 3 times a week - sometimes more, sometimes less - I get a warning
of an ID 4226 event with the source given as Tcpip. I understand that these
warnings are given as a result of more than 10 failed attempts by a process
to connect outwards.
Microsoft suggests a check on which program is attempting this, in case it's
malicious. After much research, I discovered how to open the command prompt
(!), and how to look for processes with open connections using 'netstat -no'
(I was so proud!!). But of course what I see are the processes operating NOW
- not those that triggered the Tcpip warning several hours ago. So I can't
understand how I will ever be able to discover what process is responsible,
because I only ever see the Tcpip warning long after the event occurred. Am I
missing something crucial? Surely I must be?
To be honest, I doubt if this is a malicious process. I've run Symantec,
Kaspersky and Ewido online scanners; I've scanned with Adaware, Spybot,
Defender and the MS malicious software removal tool; and I have Norton and
Defender running in real time. They all detect nothing. But still - I'd like
to track down the blighter that's doing this, just so I can say it didn't
defeat me! Can anyone point me in the right direction, please?
noticed it if I hadn't been focusing on Defender issues in the last couple of
weeks - so here goes.
Because I've been looking at Event Viewer frequently, I've noticed that
maybe 2 or 3 times a week - sometimes more, sometimes less - I get a warning
of an ID 4226 event with the source given as Tcpip. I understand that these
warnings are given as a result of more than 10 failed attempts by a process
to connect outwards.
Microsoft suggests a check on which program is attempting this, in case it's
malicious. After much research, I discovered how to open the command prompt
(!), and how to look for processes with open connections using 'netstat -no'
(I was so proud!!). But of course what I see are the processes operating NOW
- not those that triggered the Tcpip warning several hours ago. So I can't
understand how I will ever be able to discover what process is responsible,
because I only ever see the Tcpip warning long after the event occurred. Am I
missing something crucial? Surely I must be?
To be honest, I doubt if this is a malicious process. I've run Symantec,
Kaspersky and Ewido online scanners; I've scanned with Adaware, Spybot,
Defender and the MS malicious software removal tool; and I have Norton and
Defender running in real time. They all detect nothing. But still - I'd like
to track down the blighter that's doing this, just so I can say it didn't
defeat me! Can anyone point me in the right direction, please?