Do i allow NT Kernel

Status
Not open for further replies.

martinlw

Posts: 142   +5
My firewall keeps asking wether to allow NT Kernel and system, not knowing what this is its been blocked, is this correct or is it something vitally needed?
 
Hi

If you're running any version of NT or 2k/xp, it's probably just your operating system trying to do a loopback with itself, especialy if the address it wants to contact is 127.0.0.0 or similar. This is harmless and it's also neccessary for the computer to run correctly. If it's an address on the internet it wants to get to, allowing it to do so is up to you. It may also be trying to get an ip address if you have your system set up to do dhcp, wich might also be what you're seeing. If the address it wants to contact is say like 192.168.1.1, it's (usualy) trying to get a dhcp issued ip address by "leasing" one from the router or whatever does dhcp for your system.

What is the address it's trying to reach?
 
Its attempting to come in the path my firewall quotes is c windows system 32 Ntoskrnl.exe whatever that is.
 
Task manager dosent show it,also the address it shows is my own assigned by DHCP.My firewall even though it is instructed to allow for some uknown reason is blocking it. comes up in a window quite alot.
 
Sygate free edition,have now discovered alot of people with sygate 5.6 are having the same problem since upgrading from 5.5 edition.
 
Firewall permissions

I have recently switched from Sygate (new version was locking up) to Agnitum Outpost Firewall. I would appreciate some help on knowing what to block and what to allow.


It shows:
Generic Host Process for Win32 (set to always block)
LSA Shell (no setting)
Messenger 4.7 (Always block)
Application Layer Gateway (no setting)
msn.exe (no setting)
clientsideproxy (msn webaccelerator - always allow)
MSN Messenger 6.2 (always allow)
MSN Internet Service (no setting)

There are several svchost tasks that were blocked, as well as Netbios. Do these need to be allowed?

Thanks,

Brian
 
As far as I know, ntoskrnl.exe doesn't need to connect anywhere, at least if you're not sharing any files in a network.

However, it could be useful to allow ntoskrnl to IP address 0.0.0.0 only, in order to avoid duplicate IP addresses from DHCP server.

I've set my firewall to block all traffic in & out from lsass.exe, svchost.exe and ntoskrnl.exe, except ntoskrnl to 0.0.0.0 and svchost.exe to my router.
 
hi i keep getting the same message about nt kernal and system ? tried everything but it keeps blocking it really annoying shall i allow it .annoying message keeps comeing up no matter what i do this message pops up? any ideas please
 
Status
Not open for further replies.
Back