But I’m a big believer in the right tool for the job. We have a number of tools at our disposal, including Windows PowerShell. This information can be used to determine which process (program) listens on a given port.Managing processes on remote computers is a typical task for the IT Pro. The Netstat.exe command has a switch, that can display the process identifier (PID) that is associated with each connection to identify port conflicts. Here is a normal situation where EveryonePrint Web service is using TCP port 9443.

Now we can query task list to find the process. Process with PID 1400 is listening on TCP port 9443. To match the process ID to a program using the command line:Įxample to find which process uses TCP port 9443:

You should be able to easily find the process ID and match it to the program that is listed in Task Manager.

Click the column header that is labeled 'PID' to sort the process by their PIDs.

If you do not have a PID column, click View, click Select Columns, and then click to select the PID (Process Identifier) check box.

Press CTRL+ALT+DELETE, and then click Task Manager.

To match the process ID to a program using Task Manager: Because this specific port is in use already by a program, another program is prevented from using that same port. This feature enables you to find the specific port that a program currently uses. If you use Task Manager, you can match the process ID that is listed to a process name (program).

Look-out for the TCP port in the Local Address list and note the corresponding PID number.

You'll get an output similar to this one.

Type in the command: netstat -ano -p tcp.

This information can be used to determine which process (program) listens on a given port. The Netstat.exe utility has a switch, that can display the process identifier (ID) that is associated with each connection to identify port conflicts.

Task manager cmd