13:59:27 -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 fq
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 f
I think that it is the tcpd wrapper that does reverselookup, and not the
telnet or other utilities. Try removing the tcpd from /etc/inetd.conf,
ofcourse you will be loosing some security features.
tjordan wrote:
> Any idea how to keep it from doing this? Most of our machines (win95)
> are
> co
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 host
I tried this with one workstation and it cleared up the problem from that
workstation right away. That seems to be the problem in a nutshell.
I'm still wondering, though, if there's some other way to discourage the box
from doing a reverse lookup for each IP. I really don't want to have to ente
April 06, 1998 2:16 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Telnet hesitation
>
> I don't have an answer for you, but I have had (and am currently having)
> the
> same problem.
>
> The same situation occurs for HTTP and FTP connections as well. Oddly
> enou
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
> c
On Mon, 6 Apr 1998, Dave Price wrote:
> 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 tha
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 under
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 but
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 sessi
I don't have an answer for you, but I have had (and am currently having) the
same problem.
The same situation occurs for HTTP and FTP connections as well. Oddly enough,
ping response is just fine ( < 4ms over 10BaseT link)
If you find a resolution, please post it to the list.
Thanks,
Tom
>=
12 matches
Mail list logo
