Process, port, protocol RRS feed

  • Question

  • Hello!

    I have following question: may be somebody knows  - how does OS Windows allocate TCP/UDP ports to various processes? For example, some utilities (TCPView or CurrPorts) give such information:

    port          process          protocol

    135          svchost.exe     TCP

    1026        svchost.exe     TCP

    1027        svchost.exe     TCP

    1067        svchost.exe     TCP

    1054        servises.exe    TCP

    1055        lsass.exe        TCP      etc.

    But after reboot 4-th process (1067  svchost.exe   TCP) has already another port 1051, also process servises.exe (old 1054, new 1038), the rest of us - invariable.

    Does anybody know - Are old and new ports connected among themselves? May be they belong same range?


    Wednesday, April 20, 2011 1:01 PM