Every once in a while we run into a situation where one service or another doesn't seem to get their designated port for listening.
When a port conflict happens, we use a Microsoft tool called PortQry to diagnose which service is jumping in on the port before the service that needs to use that port.
KB 832919 New features and functionality in PortQry version 2.0 explains the full features and their use for the command line version. About 3/4 of the way down is the PortQry local explanation.
KB 310099 Description of the Portqry.exe command-line utility. A brief description of the utility and its features.
The download: PortQry Command Line Port Scanner 2.0.
There is a GUI for the utility, though we don't really use it. It can be found here: PortQryUI - User Interface for the PortQry Command Line Port Scanner.
This is a required troubleshooting tool for our technicians.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.
2 comments:
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.
Also, the TCP/IP tab in Process Explorer also tells you the per-process use of TCP/IP. Really handy when dealing with malware.
Looks like I'm adding PortQry 2.0 to my toolset.
The SysInternal tools do work really well.
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.
Thanks,
Philip
Post a Comment