tag:blogger.com,1999:blog-5976686513564131325.post8647770782274410374..comments2024-03-17T15:34:05.492-06:00Comments on MPECS Inc. Blog: SBS - Troubleshooting port issuesPhilip Elder Cluster MVPhttp://www.blogger.com/profile/06082028960643490292noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5976686513564131325.post-1591483928760134932007-09-06T21:54:00.000-06:002007-09-06T21:54:00.000-06:00The SysInternal tools do work really well.I find t...The SysInternal tools do work really well.<BR/><BR/>I find that something like PortQry works really well in a remote session as I don't have to worry about scrolling info plugging up the pipe.<BR/><BR/>Thanks,<BR/><BR/>PhilipPhilip Elder Cluster MVPhttps://www.blogger.com/profile/06082028960643490292noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-47319209888521778382007-08-31T19:46:00.000-06:002007-08-31T19:46:00.000-06:00Nice! I completely forgot about PortQry when I cam...Nice! I completely forgot about PortQry when I came across Sysinternals' TcpView - which lists all the TCP and UDP ports in their various states, but more importantly tells you which process is using the port.<BR/>Also, the TCP/IP tab in Process Explorer also tells you the per-process use of TCP/IP. Really handy when dealing with malware.<BR/><BR/>Looks like I'm adding PortQry 2.0 to my toolset.stryqxhttps://www.blogger.com/profile/11725668205462749500noreply@blogger.com