Here's the line from netstat: tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 419/inetd I don't have lsof as a command. Was that a typo or an addon? The netstat printout makes sense as I know that inetd can see incoming packets and thinks they are for telnet, but cann't successfully start in.telnetd. (an aside to Asheesh, yes I have the telnet server installed. That's where in.telnetd comes from.) Lyle -----Original Message----- From: Matthew Micene [mailto:[EMAIL PROTECTED]] Sent: Friday, September 08, 2000 7:13 PM To: [EMAIL PROTECTED] Subject: Re: [expert] telnet server not working... On Fri, 08 Sep 2000, you wrote: > Any suggestions to figure out what is loaded that would grab tcp port 23? as root: lsof | grep 1024 will tell you what has bound to port 1024 (as well as some other stuff) as will netstat -nlp --inet to give you the list of open ports listening for both tcp and udp and the -p option will also attempt to give you the process name as well. A combination of these two methods should tell you whether or not something else is trying to run on port 23, tho I sincerely doubt anyone would stomp all over a well known port reservation like that.... -- Matthew Micene Systems Development Manager Express Search Inc. www.ExpressSearch.com ____________________________ A host is a host from coast to coast, and no one will talk to a host too close Unless the host that isn't close is busy, hung or dead
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
