my own host is trying to connect to itself TCP 113 port

my own host is trying to connect to itself TCP 113 port

Post by Piotr Kowalsk » Sat, 07 Jun 2003 15:23:56



Hi!

I've observed that for a while my host is trying to connect to itself TCP
113 port.
/var/log/messages:

Jun  6 04:28:24 myhost /kernel: Connection attempt to TCP 1.2.3.4:113 from
TCP 1.2.3.4:2584
Jun  6 06:03:28 myhost /kernel: Connection attempt to TCP TCP 1.2.3.4:113
from TCP 1.2.3.4:2601
Jun  6 06:48:59 myhost /kernel: Connection attempt to TCP TCP 1.2.3.4:113
from TCP 1.2.3.4:2607

How can I record (if this trials go on) what process was trying to do that?
Is there sth I can do now?

pk

 
 
 

my own host is trying to connect to itself TCP 113 port

Post by Francis GUDI » Sat, 07 Jun 2003 22:23:07



Quote:> Hi!

> I've observed that for a while my host is trying to connect to itself TCP
> 113 port.
> /var/log/messages:

> Jun  6 04:28:24 myhost /kernel: Connection attempt to TCP 1.2.3.4:113 from
> TCP 1.2.3.4:2584
> Jun  6 06:03:28 myhost /kernel: Connection attempt to TCP TCP 1.2.3.4:113
> from TCP 1.2.3.4:2601
> Jun  6 06:48:59 myhost /kernel: Connection attempt to TCP TCP 1.2.3.4:113
> from TCP 1.2.3.4:2607

> How can I record (if this trials go on) what process was trying to do that?
> Is there sth I can do now?

> pk

Hello,
This originates in the local mail delivery processing : the MDA tries to
ask sthg to your identd (not running there obviously). You can safely
ignore it, or try to make use of one of several available identd-like
ports.

Francis.

 
 
 

my own host is trying to connect to itself TCP 113 port

Post by DrCla » Sat, 07 Jun 2003 22:52:24


man sockstat

That will tell you what process is listening to / connected to what port.

HTH

Quote:> How can I record (if this trials go on) what process was trying to do
that?
> Is there sth I can do now?

 
 
 

my own host is trying to connect to itself TCP 113 port

Post by Lars Tunkran » Fri, 13 Jun 2003 06:55:47



> Hi!

> I've observed that for a while my host is trying to connect to itself TCP
> 113 port.
> /var/log/messages:

> Jun  6 04:28:24 myhost /kernel: Connection attempt to TCP 1.2.3.4:113 from
> TCP 1.2.3.4:2584
> Jun  6 06:03:28 myhost /kernel: Connection attempt to TCP TCP 1.2.3.4:113
> from TCP 1.2.3.4:2601
> Jun  6 06:48:59 myhost /kernel: Connection attempt to TCP TCP 1.2.3.4:113
> from TCP 1.2.3.4:2607

> How can I record (if this trials g#Oo on) what process was trying to do that?
> Is there sth I can do now?

   This is likely  sendmail  that tries to connect to the IDENT protocol
server.

  You can stop this by telling sendmail not to use  IDENT.

   set

   O Timeout.ident=0s

    in /etc/mail/sendmail.cf

   line 339 in the stock sendmail.cf  file shipped with FreeBSD 5.1

   Or better  build you own
   Sendmail Macro Config  in

   /usr/src/contrib/sendmail/cf/cf

    and generate you own Sendmail.cf

    Manual in  /usr/src/contrib/sendmail/cf/README

     //Lars

 
 
 

1. Port 113 IDENT Do I need it open if I am running a Web/Mail Sever?

Hi guys.. Do i need oirt 113  Ident open if I am running  a mail/web
server? This is what GRC says about it

"Identification/Authorization Service Internet servers such as POP,
IMAP, SMTP, and IRC query this port in response to client
connections."

So, according to the above, it gotto stay open right? Some people say
it can be closed without affecting your DNS, Mail, Web servers, while
others says it got to be open.

thanks

2. Is CGI WRAP the only of it's kind?

3. How to Make Xinetd Stop Trying Port 113

4. Gated problems

5. TCP Port 113

6. NNTP Proxy - can it be done?

7. Help need port 113 for tcp and udp

8. Is Creative CDRW RW8433E ATAPI compatible with Cdrecord?

9. Q: What about ident/auth (113/tcp)

10. _X11TransSocketINETConnect: Can't connect: errno = 113

11. _X11TransSocketINETConnect: Can't connect: errno=113

12. Multiple access to my port 113 : hack ?

13. What is port 113 auth for?