Geekzone: technology news, blogs, forums
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

2784 posts

Uber Geek
+1 received by user: 121

Topic # 31277 11-Mar-2009 13:54
Send private message

I had a good app a while ago that would show which processes were currently using a given TCP/UDP port, and how much traffic it was moving, can't for the life of me find it again. I was trying to identify why a supposedly idle system here was shifting about 50Mb of data every 10 minutes or so and wanted to know what process(es) were using all the traffic so I could fix the problem.

Basically something akin to a realtime netstat -a -n. "Open Ports Scanner".

Any ideas? (Free is good, otherwise I have to go through mindless beaurocracy...)

Create new topic
8027 posts

Uber Geek
+1 received by user: 387


  Reply # 200617 11-Mar-2009 14:35
Send private message

Have a look at

It doesn't show the process causing the traffic but does show source port etc.

643 posts

Ultimate Geek

Reply # 200628 11-Mar-2009 15:21

netstat -b will show process names, combine with -a and you can see process names with listening ports.

for a realtime-ish view use something like 'netstat -a -b -n 1' which will not reverse lookup and re-display every 1 second.

you must be using an OS with more holes than swiss cheese.Tongue out

Sniffing the glue holding the Internet together


63 posts

Master Geek
+1 received by user: 6

  Reply # 200649 11-Mar-2009 16:31
Send private message

If you're on a Windows platform then Process and Port Analyzer from

might meet your needs, Wireshark is another good option if you're wanting detailed analyse of network traffic but it won't help in figuring out which process is actually generating the traffic

2784 posts

Uber Geek
+1 received by user: 121

  Reply # 200706 11-Mar-2009 20:34
Send private message

Cheers, looks like an unfortunate downside is that most of the good tools are written to run on XP and Vista breaks pretty much all of them (Winsock changes I assume).

The problem in the end was McAfee's update process, something went wrong and despite the fact it was reporting a successful update, something wasn't taking a note of the fact and every 5 minutes the update server dumped a 58MB update file down the pipe. Not too big a deal over the local network, but got expensive when users insisted on leaving their Telecom wireless card connected all day over VPN.

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:

Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:

Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:

Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.