![]() ![]() TCPView provides a more informative and conveniently presented subset of the Netstat program that ships with Windows. On Windows Server 2008, Vista, and XP, TCPView also reports the name of the process that owns the endpoint. Which one to choose? Start with TCPView and move on to CurrPorts if first one is not enough.TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints on your system, including the local and remote addresses and state of TCP connections. It is simply more suitable for instant action while another one is more suited for long and thorough research.Īm I willing to cut one? I may cut CurrPorts despite all those functions (I rarely need), but I know that following moment Murphy’s law is going to kick in and serve me with problem out of TCPView reach. :)ĬurrPorts has more bells and whistles but actually I always start TCPView first. Also from my experience TCPView is more reliable for killing connections - which is common outcome of network troubleshooting. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |