There should *be* a firewall between me and the host, but as you and another poster pointed out, it must be that a router is completely blocking port 98 somewhere along the lines. Strange, but I guess it's not unreasonable.
noah On Fri, Oct 13, 2000 at 10:51:07AM -0700, Mike Halderman wrote: > > A firewall before your machine is filtering that port? > > -mike > > "Noah L. Meyerhans" <[EMAIL PROTECTED]> writes: > > > Hey all. I'm seeing odd results when I portscan my server from a remote > > host. nmap is indicating that port 98 (the dreaded linuxconf port) is > > in a filtered state. I have never ever ever installed linuxconf. I > > know my ipchains rules have nothing to do with this, as I just flushed > > all the rules, tried the portscan again, and saw the same results. > > > > fuser does not show any process listening on port 98. I built a new > > fuser executable from trusted source (the Debian potato sources, freshly > > downloaded) and still saw nothing on that port. > > > > telnetting to that port from a remote host hangs while trying to > > establish the connection. telnetting from the localhost gives a > > connection refused message. > > > > I doubt it's a sign that the box has been cracked, but I suppose it's > > conceivable. I'm stumped. Can anybody offer an explanation? > > > > thanks. > > noah > > > > -- > > _______________________________________________________ > > | Web: http://web.morgul.net/~frodo/ > > | PGP Public Key: http://web.morgul.net/~frodo/mail.html > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- _______________________________________________________ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html
