RayPoynter
New Member
Hello,
I have been trying to dig up some information about why NTOSKRNL.EXE was trying to access TCP 2100 from a firewall log yesterday. Combing through Google, I found nothing!
First of, I am on a WinXP Pro SP2 machine, testing a Sygate personal Firewall.
I recieved this pop-up yesterday regarding ntoskrnl.exe.
Someone at Remote IP Address: 62.22.75.4 using TCP port 1921 was trying to access ntoskrnl.exe through TCP 2100.
Of course, I blocked this, but was curious to know, what was going on.
Any clues?
In addition, I have done the norm, scanned, scanned, scanned, and then some more scans. All with different AV, Trojan, Spyware, etc tools, system is clean.
I have been trying to dig up some information about why NTOSKRNL.EXE was trying to access TCP 2100 from a firewall log yesterday. Combing through Google, I found nothing!
First of, I am on a WinXP Pro SP2 machine, testing a Sygate personal Firewall.
I recieved this pop-up yesterday regarding ntoskrnl.exe.
Someone at Remote IP Address: 62.22.75.4 using TCP port 1921 was trying to access ntoskrnl.exe through TCP 2100.
Of course, I blocked this, but was curious to know, what was going on.
Any clues?
In addition, I have done the norm, scanned, scanned, scanned, and then some more scans. All with different AV, Trojan, Spyware, etc tools, system is clean.