On Wed, 2007-04-11 at 14:52 -0400, Bob Johnson wrote:
On 4/10/07, Jonathan McKeown [EMAIL PROTECTED] wrote:
On Monday 09 April 2007 17:37, Martin Hudec wrote:
Siju George wrote:
How Do you actually Identify what process is listening on a TCP/IP port?
nmap does not usually give the
On 4/10/07, Jonathan McKeown [EMAIL PROTECTED] wrote:
On Monday 09 April 2007 17:37, Martin Hudec wrote:
Siju George wrote:
How Do you actually Identify what process is listening on a TCP/IP port?
nmap does not usually give the right answer.
There should be some command that can be run on
In the last episode (Apr 11), Bob Johnson said:
On 4/10/07, Jonathan McKeown [EMAIL PROTECTED] wrote:
On Monday 09 April 2007 17:37, Martin Hudec wrote:
Siju George wrote:
How Do you actually Identify what process is listening on a
TCP/IP port? nmap does not usually give the right
On Monday 09 April 2007 17:37, Martin Hudec wrote:
Siju George wrote:
How Do you actually Identify what process is listening on a TCP/IP port?
nmap does not usually give the right answer.
There should be some command that can be run on the local host for
identification right?
man lsof
On Apr 10, 2007, at 3:00 AM, Jonathan McKeown wrote:
On Monday 09 April 2007 17:37, Martin Hudec wrote:
Siju George wrote:
How Do you actually Identify what process is listening on a TCP/
IP port?
man lsof
Just out of interest, why do so many people recommend lsof, which
is a port,
Hi,
How Do you actually Identify what process is listening on a TCP/IP port?
nmap does not usually give the right answer.
There should be some command that can be run on the local host for
identification right?
Thankyou so much
kind Regards
Siju
___
In response to Siju George [EMAIL PROTECTED]:
How Do you actually Identify what process is listening on a TCP/IP port?
nmap does not usually give the right answer.
There should be some command that can be run on the local host for
identification right?
sockstat -4
Various magical
Siju George wrote:
How Do you actually Identify what process is listening on a TCP/IP port?
nmap does not usually give the right answer.
There should be some command that can be run on the local host for
identification right?
man lsof
5:35pm [amber] ~# lsof -i @localhost:123
COMMAND PID USER
In the last episode (Apr 09), Siju George said:
How Do you actually Identify what process is listening on a TCP/IP
port? nmap does not usually give the right answer. There should be
some command that can be run on the local host for identification
right?
Try /usr/bin/sockstat or lsof (in
