On Wed, Dec 14, 2005 at 11:18:29PM -0600, Jeffrey L. Taylor wrote:
Quoting Alex Pankratz [EMAIL PROTECTED]:
[snip]
Did, and that made both 111 and 699 not show up in nmap scan. sweet,
thanks Jeffery. I could swear that in the past I saw 111 open and I
sort of ignored it, why would 699 be open now,
My apologies in advance if this is the wrong place to ask this, this
is my first time asking for help..
What is running on port 699? I only have squid, ssh, and dhcpd
listening on my 2 internal interfaces, but nothing on my external one
(XXX.XXX.XXX.XXX below)
I just ran nmap, and it returned:
See interspersed comments below.
Quoting Alex Pankratz [EMAIL PROTECTED]:
My apologies in advance if this is the wrong place to ask this, this
is my first time asking for help..
What is running on port 699? I only have squid, ssh, and dhcpd
listening on my 2 internal interfaces, but nothing
See interspersed comments below.
My replies interspersed
Quoting Alex Pankratz [EMAIL PROTECTED]:
My apologies in advance if this is the wrong place to ask this, this
is my first time asking for help..
What is running on port 699? I only have squid, ssh, and dhcpd
listening on my 2
Quoting Alex Pankratz [EMAIL PROTECTED]:
[snip]
Did, and that made both 111 and 699 not show up in nmap scan. sweet,
thanks Jeffery. I could swear that in the past I saw 111 open and I
sort of ignored it, why would 699 be open now, and then closed? why is
statd running, i dont use NFS.
There
In article [EMAIL PROTECTED] you wrote:
netstat -na | grep 699
tcp0 0 0.0.0.0:699 0.0.0.0:* LISTEN
if you run it as root and use netstat -lnpo it will give you the pid and
process name of the open listening socket.
In some rare cases netstat wont help,
6 matches
Mail list logo