by Bill_Castner » December 16th, 2006, 7:32 pm
Make sure that the Windows Messenger service is stopped, and its startup desposition set to disabled. You can use the Services applet for this chore.
Other than that, what you are looking at is the Windows kernel. It needs TCP and UDP 135, 136, 137, 139 and 445 for Netbios name resolution with Windows Networking, and 445 for RPC calls.
. Disable Windows File and Printer sharing if not used. The selection box is under Network Connections, your existing LAN or Wireless connection, right-click, Properties.
. Windows Messenger service has nothing to do with the Messenger IM client. Under SP2 its default status should be set to disabled.
. It is fine if Windows Networking sits on these ports for internal traffic. It is not fine if it sits on these ports for WAN side traffic. The default XP firewall would have made the appropriate choices. Check your firewall settings and block any non-LAN local subnet traffic on the effected ports.
(Your kernel choices are HAL dependent and made during installation. Ntoskrnl.exe will either be the single processor example, as in your case, or the multiple processor version. The latter would appear as ntoskrnmpa).