{"id":348,"date":"2013-11-19T23:45:33","date_gmt":"2013-11-19T15:45:33","guid":{"rendered":"https:\/\/www.techcoil.com\/blog\/?p=348"},"modified":"2018-09-04T13:15:59","modified_gmt":"2018-09-04T05:15:59","slug":"steps-to-check-which-process-is-listening-on-a-port-with-windows-built-in-facilities","status":"publish","type":"post","link":"https:\/\/www.techcoil.com\/blog\/steps-to-check-which-process-is-listening-on-a-port-with-windows-built-in-facilities\/","title":{"rendered":"Steps to check whether a process had utilised a port before your application does with windows built in facilities"},"content":{"rendered":"

As a systems analyst, it is inevitable for me to go to windows based computers to check out the applications that I am taking care of. Most of my applications listen to commands via TCP\/IP ports in order to do work. <\/p>\n

Whenever a user reports that one of such applications is failing on their machine, the first thing that I will check out is whether that application is able to reserve the port that it is supposed to listen to.<\/p>\n

Although there are Sysinternal suite of diagnostic tools for me to use, there are client machines does not allow foreign executables to execute on them. <\/p>\n

This post details the steps that I take to check out whether there is a port binding issue in the event that my application fail to run in windows based machines. <\/p>\n

    \n
  1. Start command prompt. Inside command prompt, type 'netstat \u2013aon'<\/li>\n
  2. Look for the number which my application listen to, after :, and look at the last column for the pid. <\/li>\n
  3. Open up task manager. <\/li>\n
  4. In task manager, go to the processes tab. Look at the PID column. If the column is not available, go to view -> Select Column... and check on the PID option.<\/li>\n
  5. Match the pid to the one that u get from step 2) and look at the process name. <\/li>\n<\/ol>\n

    If the process name shown is not my application executable, it will mean that my application had failed to grab hold of the port for it to do work, and I can take steps to bring it up again. <\/p>\n

    If the process name shown is indeed my application executable, I can continue with the performing other debug procedures for that application.<\/p>\n\n