On Tue, 8 Feb 2000, Kenneth E. Lussier wrote:

> That's a really good question (and I wish I had an answer). I'm guessing
> that `netstat` can somehow tell you what's listening on what ports. A

$ netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 172.16.1.1:1023         206.135.68.99:1019
ESTABLISHED 
tcp        1      0 172.16.1.1:2069         208.51.139.19:80
CLOSE_WAIT  
tcp        0      0 0.0.0.0:6000            0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:1024            0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:515             0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:98              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:79              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:513             0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:514             0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:23              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      
udp        0      0 0.0.0.0:177             0.0.0.0:*                           
udp        0      0 0.0.0.0:518             0.0.0.0:*                           
udp        0      0 0.0.0.0:517             0.0.0.0:*                           
udp        0      0 0.0.0.0:111             0.0.0.0:*                           
raw        0      0 0.0.0.0:1               0.0.0.0:*               7           
raw        0      0 0.0.0.0:6               0.0.0.0:*               7           

[SNIP]

Look at the local address column... if you see 0.0.0.0:110 or
MACHINE_IP:110 with a state of LISTEN, it means something is bound to port
110. You can see that I'm running an X server (port 6000), sendmail (port
25), a web server (port 80), lpd (port 515), sshd (port 22), etc. etc. ad
nauseum.

However, the only thing that should be binding to port 110 is a pop
server, so it's unlikely that you're accidentally running something else
that has it locked up.

You can also use the -p option on RH 6.1 (and maybe other distros...) to
identify what process is associated with each open socket.


-- 
"Quis custodiet ipsos custodes?"    "Who watches the watchmen?" 
-Juvenal, Satires, VI, 347 

Derek D. Martin      |  Senior UNIX Systems/Network Administrator
Arris Interactive    |  A Nortel Company
[EMAIL PROTECTED]  |  [EMAIL PROTECTED]
-------------------------------------------------


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to