



If you run it and look in the "State" column and sort/filter for "Listen", you can find exactly the other program has that TCP port (usually 25565) occupied.

If you run it and look in the "State" column and sort/filter for "Listen", you can find exactly the other program has that TCP port (usually 25565) occupied.