When your application is not able to get the PID, it's showing 0. PID 0 doesn't actually exist, and is the PID that is shown in the PID column when looking at processes simply to show that it has no associated PID.
More commonly, people get their ports backwards. It's normal for some windows flavors to increment the source port for each new outgoing connection. This traffic looks to me like normal windows network traffic.
My recommendation is to get a better analyzer that matches up the PIDs correctly, or simply run netstat from a command prompt on your worksation.
netstat /banv
Main Topics
Browse All Topics





by: amaru21Posted on 2009-02-09 at 16:59:38ID: 23596322
Is it possible to see the payload of the packets? I'm not familiar with Process and Port Analyzer, but you may want to try Wireshark to see what's in the packets.
o.com
e/index.ph p?wpid=1&f ront_id=12 with great success.
Here is some info on the ports you listed. I'm not exactly sure why it would be scanning the other machines for these though.
System service name: Eventlog
Collapse this tableExpand this table
Application protocol Protocol Ports
RPC/named pipes (NP) TCP 139
RPC/NP TCP 445
RPC/NP UDP 137
RPC/NP UDP 138
Port 123 is NTP.
You may want to try some other virus/spyware scanners to make sure your computer is clean. Here are some I use:
http://bitdefender.com
http://housecall.trendmicr
http://malwarebytes.com
Hard to remove viruses sometimes require to scan the the hard drive as a secondary drive on a clean machine. I've also used http://trinityhome.org/Hom