Port-to-process mapping the ability to determine which processes own which ports on your system. Existing Port-to-process mapping tools besides being difficult to set up, require client software to be installed on the remote systems that you wish to access.
There are many times you'll look at the results of a port-to-process mapper and wish to know the command-line arguments a particular process has been started with. Surprisingly, none of the available port-to-process mappers provide this capability. The Only netport allows you to determine the command-line arguments of each process. netport also allows you to take MD5 hashes of the running processes.
Just copy netport onto your executable path. Executing netport with -h option displays its usage syntax.
The syntax is straightforward and easy to learn.
Arguments supplied to netps are case sensitive.
To lists all TCP and UDP ports available on the system along with their parent processes,
To retrieve port-mapping for specific ports, use the -p switch
The default output file name is netport, if no output file name is supplied with the -ox/-oc switch. To save the results of netport to an XML file with a different name,
To list only connected endpoints, type
To list command-line arguments as well as MD5 hashes of each process along with port-to-process mapping, type
netport has been tested on Windows NT 4.0 Server, Windows NT 4.0 workstation, Windows 2000, Windows XP and Windows 2003.
netps is included in a command-line toolkit named NSTools from Net-Square, that aid in the administration and audit of remote Windows NT/2K/XP/2003 systems.