You can monitor, troubleshooting which process is listening on a TCP or UDP port on Windows throughout different options but three listed below are common and recommended tools you can use?
1) TCPVIEW free simple and awosam tools. Download from link below
a) TCP Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess
b) UDP Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess
3) CMD
netstat -a -b
(Add -n to stop it trying to resolve hostnames, to allowed it to be faster)
-aDisplays all connections and listening ports.
-b Displays the executable involved in creating each connection or listening port. In some cases well-known executables host multiple independent components, and in these cases the sequence of components involved in creating the connection or listening port is displayed. In this case the executable name is in [] at the bottom, on top is the component it called, and so forth until TCP/IP was reached. Note that this option can be time-consuming and will fail unless you have sufficient permissions.
-n Displays addresses and port numbers in numerical form.
Answer ( 1 )
You can monitor, troubleshooting which process is listening on a TCP or UDP port on Windows throughout different options but three listed below are common and recommended tools you can use?
1) TCPVIEW free simple and awosam tools. Download from link below
https://learn.microsoft.com/en-us/sysinternals/downloads/tcpview
2)PowerShell
a) TCP
Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess
b) UDP
Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess
3) CMD
netstat -a -b
(Add -n to stop it trying to resolve hostnames, to allowed it to be faster)
-a Displays all connections and listening ports.
-b Displays the executable involved in creating each connection or listening port. In some cases well-known executables host multiple independent components, and in these cases the sequence of components involved in creating the connection or listening port is displayed. In this case the executable name is in [] at the bottom, on top is the component it called, and so forth until TCP/IP was reached. Note that this option can be time-consuming and will fail unless you have sufficient permissions.
-n Displays addresses and port numbers in numerical form.