[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Why s port 111 still open?

Your issue seems to be resolved. However, I'd prefer to teach a man to fish.... As it were, lsof -i :111 should show you the pid of what is on that port. From there, ps and then look through logs or 'find /etc/unit.d -type f -print0 | xargs -0 -i{} grep <p name> {}' sometimes works. But if you don't see am unit service, chances are its tcp wrapper / portmap. FWIW

On Aug 29, 2011 8:30 AM, "Tom H" <tomh0665@gmail.com> wrote:
> On Mon, Aug 29, 2011 at 5:38 AM, Lisi <lisi.reisz@gmail.com> wrote:
>> I was under the impression that I had cleansed my system of rpcbind after the
>> security discussion on this list.  Today, because I was trying to remove
>> Samba, I ran nmap to see what was going on.  Here is the "conversation" I had
>> with Tux just now:
>> lisi@Tux:~$ nmap Tux
>> Starting Nmap 4.62 ( http://nmap.org ) at 2011-08-29 10:31 BST
>> Interesting ports on Tux (
>> Not shown: 1711 closed ports
>> 22/tcp   open  ssh
>> 80/tcp   open  http
>> 111/tcp  open  rpcbind
>> 6881/tcp open  bittorrent-tracker
>> Nmap done: 1 IP address (1 host up) scanned in 0.126 seconds
>> lisi@Tux:~$ which rpcbind
>> lisi@Tux:~$ whereis rpcbind
>> rpcbind:
>> lisi@Tux:~$ locate rpcbind
>> lisi@Tux:~$ find rpcbind
>> find: `rpcbind': No such file or directory
>> lisi@Tux:~$
> CHeck whether the rpcbind or the portmap packages are installed.
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/CAOdoSy-CMkh2yRLJSo_zQUfhpsYCMFXqO8hK14sqz92bCA@mail.gmail.com

Reply to: