topic Re: Telnet is connecting slow in Operating System - HP-UX

Telnet is connecting slow

trilok_pvp — Sat, 21 Mar 2009 17:25:20 GMT

Hi

I am HP unix boxes i am unable to connect to Telnet, its takes lot of time to get the login screen. I DNS have the problem, how to fix it temp.

Re: Telnet is connecting slow

Steven Schweda — Sat, 21 Mar 2009 18:28:13 GMT

Which is it, "unable to connect" or "takes
lot of time"?

If the only slow thing is the initial
connection, then it probably is a DNS
problem. A Forum search for, say,
telnet slow
would find many similar threads.

> [...] how to fix it temp.

Why not fix it perm?

You could try adding the Telnet client
system(s) to the DNS data, or /etc/hosts on
the Telnet server system.

You might also wish to adjust
"/etc/nsswitch.conf", depending on what's in
there now.

Re: Telnet is connecting slow

trilok_pvp — Sat, 21 Mar 2009 18:52:49 GMT

Hi it takes lot of time to connect.

and in etc/nsswitch.conf file the following entries asre there

hosts: files [NOTFOUND=continue UNAVAIL=continue] dns
ipnodes: files [NOTFOUND=return] dns

Re: Telnet is connecting slow

Avinash20 — Sun, 22 Mar 2009 05:07:40 GMT

Having issue with DNS

Temp fix:

# mv /etc/resolv.conf /etc/resolv.conf.

Check the telnet now

Re: Telnet is connecting slow

Asif Sharif — Sun, 22 Mar 2009 05:38:26 GMT

In your case the telnet session may be waited for DNS timeout before looking up "/etc/hosts" to resolve the requested IP.

Try creating the file "/etc/nsswitch.conf".

Regards,
Asif Sharif

Re: Telnet is connecting slow

trilok_pvp — Sun, 22 Mar 2009 14:31:16 GMT

Hi,

I tried by moving the file and recreating the resolv.conf file. But still it takes lot of time to get the login screen.

Re: Telnet is connecting slow

Steven Schweda — Sun, 22 Mar 2009 15:00:06 GMT

> I tried by moving the file and recreating
> the resolv.conf file. But still it takes
> lot of time to get the login screen.

I think that his idea was to remove
resolv.conf, so that you wouldn't be using
DNS at all. Recreating it would mean that
nothing really changed, so I'd expect no
change in the result.

This might be a good test, but it's not what
I'd choose as a long-term solution, because
completely disabling DNS can stop too many
other things from working.

> You could try adding the Telnet client
> system(s) to the DNS data, or /etc/hosts on
> the Telnet server system.

Still true. (And, apparently, still
untried.)