Link to "Build your own netstat" is broken. Konamiman's comment has a working link: timvw. EddPorter Update: web. InteXX 5, 5 5 gold badges 34 34 silver badges 61 61 bronze badges. Konamiman Konamiman Page was not found : — Misaz. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. First method uses netstat to find pid of the process listening on specific port, then use tasklist to find process name by the pid. Use the following command to find out the process id pid listening on port You can change this port to search for another port.
The last column of the output shows the pid of the processes. The above output shows the pid is 4 for the process listening on port The second method uses PowerShell command to find out process running on specific port on Windows. Tags : windows batch-file process kill-process windows. Note that you might need to change this slightly for different OS's. This lets you execute command , and loop over its output.
Just run it and find out. According to the command line help, it "Displays all connections and listening ports. I just used these options since someone else suggested it, and it happened to work :. This takes the output of the first command or program netstat and passes it onto a second command program findstr.
0コメント