Quoting Don Sauer <[EMAIL PROTECTED]>: > Google would be a better friend if you read the question- Dave. The > correct answer is Fport from foundstone. Unlike Linux windows doesn't > match ports to pids until >Net server comes out so on NT 4 and windows > 2000 you need a utility. >
Windows XP has this capability and has done since it was released.. C:\> netstat -ano C:\> tasklist /svc -fi "pid eq <pid goes here>" But seen as though we are mostly talking about NT/2000 fport [1] is the answer, or Activeport [2] or fports gui-fied brother Vision [3]. [1] http://www.foundstone.com/knowledge/proddesc/fport.html [2] http://www.webattack.com/get/activeports.shtml [3] http://www.foundstone.com/knowledge/proddesc/vision.html > -----Original Message----- > From: Dave C [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 21, 2003 1:49 PM > To: [EMAIL PROTECTED] > Subject: Re: Associating Windows Processes to TCPIP Ports? > > > Google is our friend... > http://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=identify+TCP+port > s+to+process > > > "David Simcik" <[EMAIL PROTECTED]> wrote .. > > Hiya, > > Anyone know of a tool that can map TCP/UDP ports to a specific process > > > in Windows (NT/2000)? My apologies if this is a naive question. > > > > Thanks, > > David > > > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/
