Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am investigating a production system where there are several Windows services communicating with each other through TCP/IP sockets. I’m trying to figure out which executable is listening to which IP address and which port on a given machine.
Other than rummaging through each windows service’s obscure configuration files, is there a system tool that can more easily give me the details I want?
As already mentioned TCPView by SysInternals (i.e. Microsoft) is a great tool. But on production systems you may not be allowed to install additional software, so I think you may want to try out netstat.exe, which is typically located at C:\WINNT\system32\netstat.exe .
A help page is available with
Examples are:
Lists all local TCP connections and listening ports together with remote TCP endpoint.
Adds the process ID to the output.
Gives you the name of the executable wich was involved in establishing this connection/port.