1 | initial version |
There are some suggested tools listed here: how to follow process on Windows
And several open enhancement requests:
1184: *Shark should support associating TCP and UDP packets with processes
17525: Feature request: Add to Wireshark capability to show process IDs, process name and commandline of process(es) whose owns local side(s) of network traffic sessions.