In a message dated 98-04-06 14:21:43 EDT, you write:
Subj: Re: Telnet hesitation
Date: 98-04-06 14:21:43 EDT
From: [EMAIL PROTECTED] (Dave Price)
Reply-to: [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
Yes,
I understand that this has to do with the Target machine failing
-0500
From: tjordan [EMAIL PROTECTED]
To:Dave Price [EMAIL PROTECTED]
Subject: RE: Telnet hesitation
Any idea how to keep it from doing this? Most of our machines (win95) are
configured with IP only and don't have fqdn's associated with them through
DNS
Hi,
Has anyone ever experienced a problem where you telnet to a machine
running RHLinux, and there is an unusual amount of time (1minute)
that goes by before you get a login: prompt??
---
$ telnet machine.running.redhat
Trying machine.running.redhat...
Connected to machine.running.redhat.
Yes,
I understand that this has to do with the Target machine failing to
reverse resolve the ip address that you are telnetting from ... it
eventually times out and lets you in anyway - look at /var/log/messages on
the target - you will see that the log usually shows names (fqdn) for
telnet
I get that several times when I telnet to certain accounts at college. If
you have an external modem, you would notice that your computer keeps
sending packets for a response and there is no response for a long time.
I don't know the true explanation for this hang up, I'm not a network
expert
Any idea how to keep it from doing this? Most of our machines (win95) are
configured with IP only and don't have fqdn's associated with them through
DNS. Is there a way that you know of to avoid the name lookups?
= Original Message From Dave Price [EMAIL PROTECTED] =
Yes,
I understand
I think if you add the the client hostnames/ip addresses to /etc/hosts on
the target box it will help as long as target box /etc/resolv.conf allows
for hosts before bind
dave
On Mon, 6 Apr 1998, tjordan wrote:
Any idea how to keep it from doing this? Most of our machines (win95) are
I noticed the telnet hesitation on a 4.2 box we had here.
I also noticed that there is no hesitation when 5.0 was installed on the
same box.
Maybe someone can add to cause of the hesitation.
-Eric
-Original Message-
From: tjordan [SMTP:[EMAIL PROTECTED]]
Sent: Monday, April 06
I know of none - i think this is coded into the logging feature of the
telnetd daemon - if you looked at the sources
800+ IP addresses should be documented somehow/somewhere - perhaps a perl
script could create a hosts file - barring that, i would write a perl
script ot generate a fake
