I came across an issue with my server not listening on 3389 for terminal server access after the last update bombed the computer. I wasn't sure if the issue was because of a conflicting port so I ran the following command from a prompt:
netstat -a -o
That tells me what ports the server is listening on following by a PID number off to the right.
Then I ran:
This ties the PID to the task or service running it. Now I can see what is trying to use the port and resolve the conflict.