If we need to determine who's taking up our 9050 port,
execute under Windows command-line window:
1. View all port usage
C:\>netstat-ano
Protocol Local address external address state PID
TCP 127.0.0.1:1434 0.0.0.0:0 LISTENING 3236
TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING 4168
TCP 127.0.0.1:7438 0.0.0.0:0 LISTENING 4168
TCP 127.0.0.1:8015 0.0.0.0:0 LISTENING 1456
TCP 192.168.3.230:139 0.0.0.0:0 LISTENING 4
TCP 192.168.3.230:1957 220.181.31.225:443 established 3068
TCP 192.168.3.230:2020 183.62.96.189:1522 established 1456
TCP 192.168.3.230:2927 117.79.91.18:80 established 4732
TCP 192.168.3.230:2929 117.79.91.18:80 established 4732
TCP 192.168.3.230:2930 117.79.91.18:80 established 4732
TCP 192.168.3.230:2931 117.79.91.18:80 established 4732
2. View the usage of the specified port
c:\>netstat-aon|findstr "9050"
Protocol Local address external address state PID
TCP 127.0.0.1:9050 0.0.0.0:0 LISTENING
P: See, Port is occupied by process number 2016 process, continue to execute the following command: (You can also go to the task Manager to see the PID corresponding process)
3. View the PID corresponding process
C:\>tasklist|findstr "
Image Name PID session name Session # Memory Usage
========================= ======== ================
tor.exe Console 0 16,064 K
P: Well, it's clear that Tor is taking up your port.
4. End the process
c:\>taskkill/f/t/im Tor.exe
How Windows looks at which process the port is consuming