Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Telnet login delayed

0 views
Skip to first unread message

new...@my-deja.com

unread,
Sep 21, 2000, 3:00:00 AM9/21/00
to
Hi everyone

I installed Redhat Linux 6.2 and i enable telnet also
when i try to telnet to this server from my windows client (95 and 98)
it takes long time (almost 55 second) to show the login prompt. all PcS

ARE ON LOCAL NETWORK.

I want to reduce the Login-prompt time. How can this be achived. All

users who are using Linux server are Trusted user.

Thanks in advance

ssp99


Sent via Deja.com http://www.deja.com/
Before you buy.

Vilmos Soti

unread,
Sep 21, 2000, 3:00:00 AM9/21/00
to
new...@my-deja.com writes:

> I installed Redhat Linux 6.2 and i enable telnet also
> when i try to telnet to this server from my windows client (95 and 98)
> it takes long time (almost 55 second) to show the login prompt. all PcS

dns. Either configure a dns for your local network, or put
the ip addresses/names in /etc/hosts file.

Vilmos

Stefan Pommerening

unread,
Sep 21, 2000, 3:00:00 AM9/21/00
to
Seems to be a typical DNS problem. Check the following:

When logged in the linux box, check your source IP by
questioning 'w' command. If you get a numerical IP address
that's the problem...
Linux tries to resolve your numerical source IP and does
not succeed - therefore you get the 1 minute timeout (about).

Solution:
- Configure reverse DNS for the source IP address by
setting it up in your /var/named configuration or simply
adding this ip to your /etc/hosts file.

Stefan.


new...@my-deja.com schrieb:
>
> Hi everyone


>
> I installed Redhat Linux 6.2 and i enable telnet also
> when i try to telnet to this server from my windows client (95 and 98)
> it takes long time (almost 55 second) to show the login prompt. all PcS
>

Chris Dunlop

unread,
Sep 21, 2000, 3:00:00 AM9/21/00
to
TCP Wrappers tries various methods to make sure that your machine actually
is who it says it is before allowing a connection:

1) ip to name resolution - tcpd looks for a PTR record from it's DNS
servers.

2)name to ip resolution - tcpd then looks for the A record for that name,
looking for a match with the results of 1)

3) If tcpd was compiled to do so, it will use an AUTH inquiry to attempt to
identify the user.

See Vilmos and Stefan's recommendations to fix 1 and 2. If you are doing
AUTH lookups, you will have a delay while the AUTH lookup times out for a
Win client, and Win doesn't support inetd.

<new...@my-deja.com> wrote in message news:8qc2la$if3$1...@nnrp1.deja.com...

Sun Ju

unread,
Sep 21, 2000, 3:00:00 AM9/21/00
to
Disable the Reverse Name resolution would be a better choice.
You may telnet from different locations.
But if you just telnet from one place, just put the follow that instruction.

Josh


> new...@my-deja.com writes:
>
> > I installed Redhat Linux 6.2 and i enable telnet also
> > when i try to telnet to this server from my windows client (95 and 98)
> > it takes long time (almost 55 second) to show the login prompt. all PcS
>

Thomas Martin

unread,
Sep 22, 2000, 3:00:00 AM9/22/00
to
Thanks for the tip. I was having the same problem. Gone now..

Tommy

"Vilmos Soti" <vil...@vilmos.org> wrote in message
news:m3n1h2q...@ppro.vilmos.lan...

0 new messages