News Collaboration Media Projects DevNotes   Audio/Video   Graphics   Internet   Prog. Lang.   Tips/Misc. BetaWorks   Magic Video Project   ImageScape   LML Website(NEW) Research   Content Based Retrieval   Interactive Video   Speech Interfaces   Virtual Studio People Archive	Network Problems and Diagnosis by: (2 Apr 2015) This article gives some tips on checking what is using your ports and which services started them. Another common scenario we come across is port blocking and/or port assignment conflict. To diagnose this problem, you not only want to check whether the default RDP port (3389) is blocked; you also want to make sure that it's being used by the appropriate service (TermService, in this case). Here's a quick test that uses the Netstat and Tasklist commands, which you run on the server that you're trying to connect to remotely: C:\Users\Administrator.CONTOSOONE>netstat -a -o Active Connections Proto Local Address Foreign Address State PID TCP <IP address>:3389 <Server Name>:0 LISTENING 2252 The results show that the server is listening on port 3389. If port 3389 isn't listed, the server isn't listening on that port (possibly due to a host-based firewall or another ACL mechanism on the host machine that prevents the usage of that port). But confirming that the port is open is only half of the battle. You still need to make sure that the right service is using that port. So, you grab the Process ID (PID) number from the results and run Tasklist while grep’ing for PID 2252. C:\Users\Administrator.CONTOSOONE>tasklist /svc | findstr "2252"		Research Links Media Lab Overview LIACS Homepage MM Conf ACM Multimedia ACM ICMR IAPR ICPR Science Direct IEEE Library LIACS Publications ACM Digital Library