![]() ![]() CurrPorts offers a lot but horizontal scroll is required to view it all… Alternative to scroll is spending time at configuring and tuning. TCPView constantly refreshes list by default while CurrPorts needs this option found and turned on manually. It outputs more information and has few times more columns, allows to set complex filters, has more export options and even some CLI functions.ĬurrPorts clearly wins functions war but when you start using these apps some sudden subtle differences show up in favor of TCPView. ![]() Both have simple and informative GUI (it’s hard to re-invent list-of-whatever-with-columns).Īs soon as you start clicking around CurrPorts suddenly has more buttons to push. TCPView is larger, but 145Kb is fine even by ancient floppy grade. They are lightweight, single-file, portable. While I try to stick with single application for specific task I ended up with two for monitoring network connections TCPView (of Sysinternals) and CurrPorts (of NirSoft).īoth apps have a lot in common. Windows itself can barely identify if connection is working at all, monitor utilities are usually more occupied with counting traffic. ![]() There may be different reasons (connection trouble, slow browsing, simple curiosity, etc) that raise the very same question - what is happening with network connection right now? ![]()
0 Comments
Leave a Reply. |