Re: Port 699 listening

2005-12-15 Thread Aníbal Monsalve Salazar
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,

Re: Port 699 listening

2005-12-14 Thread Jeffrey L. Taylor
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

Re: Port 699 listening

2005-12-14 Thread Alex Pankratz
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

Re: Port 699 listening

2005-12-14 Thread Jeffrey L. Taylor
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

Re: Port 699 listening

2005-12-14 Thread Bernd Eckenfels
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,