It's attacking the other computers on port 139 trying to get access to the NetBios. Like clockwork, every 13 minutes.
Are you on some sort of network at work or something? What firewall are you using? Anyone know of a good free firewall other than Sygate that folks can download without screwing up their box I know that when M$ did it's last automatic update on XP Pro that their latest firewall mis-adjusted my dial up connection and Bell South told me not to use M$ firewall. That is exactly why I need to move to MAC ASAP when I can afford it.
Sometimes clearing the Temporary Internet Files & History cache in IE (Tools | Internet Options) will clear the problem with viewing source that refuses to load. It's a bug in IE IMO. Sometimes when the View | Source menu option does not work, preceding the URL with view-source: in the address bar will work.
Why would one use a M$ Windows OS/IE in the first place Crazy Rob, we must be Crazy, Crazy Bernard, I did that also and then was able to view the source, but it could have also been spyware that was in the registry because when I ran Adaware it seemed to come back. Who knows anymore Bernard, it could be anything with Windows
Rememeber to turn off your internet connection while deleting spyware! I even do that when I run spybot on someones computer just to make sure nothing new is installed during the delete. I have so far not had anything on my main computer, but since I run my business off of it I am very careful what I download or install. I even researched spybot before installing it.
FWW, M$ said that Bell South had not patched their software to deal with M$ firewall that was automatically installed in an XP Pro update and enabled by default. When I rebooted the machine after the update I lost my internet connection because the firewall was on and had to turn the firewall off (Bell South said not to use it) and reset my dial up connection again to get back online. Just have a simple dial up connection, no home networking.
There are network monitoring tools (free) on downloads.com which helped me determine which programs send what info to who. Then it's easy to trace who's the culprit. I forgot the name of the program I used but a search like 'network monitoring' or ' network packet monitoring' should yield some results.