It may not be the /etc/hosts.deny file.
Something may be trying to log telnet sessions with the client hostname
rather than the client ip address. Thus, reverse DNS look ups are
necessary.
If my memory serves me correctly, I saw hostnames instead of ip
addresses in my /var/log/daemon.log for tel
Patrick Colbeck wrote:
> Yup
>
> I think the telnetd tries to do a reverse lookup on the incoming telnet
> session. Adding your ip address and machine name to the hosts file of the
> machine you are telneting to will speed it up a lot. Same thing applies to
> proftpd so maybe its a function of the
Indeed. You need either a properly reverse zone nameserver or add the
entries to hosts file.
Martin.
> -Original Message-
> From: Patrick Colbeck [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 05, 2001 10:57 AM
> To: Jason P. Holland; 'Debian User list'
> Sub
Yup
I think the telnetd tries to do a reverse lookup on the incoming telnet
session. Adding your ip address and machine name to the hosts file of the
machine you are telneting to will speed it up a lot. Same thing applies to
proftpd so maybe its a function of the inetd super server ?
Pat
On
This is normally associated with DNS problems. check and make sure you have
/etc/resolv.conf setup correctly. Also, if you need a static entry or two,
add them to /etc/hosts.
Jason
>
> I'm having difficulty telnetting into my system. It appears
> that I get a
> connection right away, but it ta
I'm having difficulty telnetting into my system. It appears that I get a
connection right away, but it takes a long time to receive the login prompt
and often I don't receive a prompt at all. Any advice would be appreciated.
Bill
6 matches
Mail list logo
