topic Re: telnet problem in Operating System - HP-UX

telnet problem

radi_1 — Sun, 26 Nov 2006 08:40:59 GMT

Hi,
I have the following situation;
server:G-class
o.s :11.0
hostname:g41
Active users:40
When telnet the server the connection is established
without any delay and the following message is displayed:

connecting to host g41
connection established
HP-UX g41 B.11.00 U 9000/867

The login: prompt takes 15 seconds to appear,
and when logged in, the login process is delayed for 10 seconds before it starts ,and while user is logged in the speed of application
transactions is normal, and finally when logging out it takes 15 seconds to complete.

Why it takes too long to get login: prompt and to logout?

Thanks in advance.

Re: telnet problem

Duncan Edmonstone — Sun, 26 Nov 2006 09:05:49 GMT

Wow, a G-class - didn't think there were any of these left out there!

Anyway maybe you have a name resolution problem - I'd checkout your DNS config.

HTH

Duncan

Re: telnet problem

James R. Ferguson — Sun, 26 Nov 2006 09:13:32 GMT

Hi Radi:

I agree with Duncan. DNS is the first thing that comes to mind. If you can connect and login quickly using an IP address but now using a (host)name, look at your DNS configuration. You may need to add reverse lookup records.

Regards!

...JRF...

Re: telnet problem

radi_1 — Sun, 26 Nov 2006 09:14:06 GMT

Hi Duncan,
DNS is not configured on the server,also the /etc/nnswitch.conf is setup to use first /etc/hosts .

Re: telnet problem

Bill Hassell — Sun, 26 Nov 2006 14:11:04 GMT

To verify that DNS is not being used, run nslookup with a local hostname and then some external hostname like www.hp.com. The local hostname will showup immediately with text like this:

Using /etc/hosts on: myg30
looking up FILES
Name: localcpu
...

Also check with nsquery:

nsquery hosts www.hp.com

This will show you how hosts and IP addresses will be resolved. If you see fallback to a DNS server, then your system has been configured to use DNS (or NIS).

Just to make sure, remove the file /etc/resolv.conf if it exists. You can also remove /etc/nsswitch.conf too. The 15 second delay (probably closer to 20 secs) is the classic delay experienced when an unknown remote host tries to connect and the IP address is tested for validity using /etc/hosts or other nameservers.

Re: telnet problem

radi_1 — Mon, 27 Nov 2006 09:21:41 GMT

Hi ,
I have run the nslookup ,it uses /etc/hosts file.
I have removed nsswitch.conf & resolve.conf files but still no improvement on login time.
What seems to be the problem?
Can anybody tell me what scripts or file are
executed before a login prompt is displayed and why there is delay in user login time(i.e after user gives his user name and password?)
Thanks

Re: telnet problem

Christian Tremblay — Mon, 27 Nov 2006 10:34:36 GMT

What is the load on your server,check it with top. If there is a process or app that uses most system resources, then you may experience delays in logins.

Re: telnet problem

Roland Piette — Mon, 27 Nov 2006 11:00:53 GMT

Hi Radi,

Look also your connection hardware. As admin use lanadmin and control error value with display option. Check also that bothare working at the same speed, same duplex mode.
My opinion : don't use auto negociation !

I hope it helps,
Roland

Re: telnet problem

KUMAR_13 — Mon, 27 Nov 2006 18:43:57 GMT

Dear,
It Happened wid me...
Checked for DNS Config... HWRE Probm cud be..
Check wd Ping... from some other server n watch package n time..

Still Problem let me know...

Re: telnet problem

Bill Hassell — Mon, 27 Nov 2006 20:47:20 GMT

> Can anybody tell me what scripts or file are
executed before a login prompt is displayed

For telnet connections, login is the only program. Prior to login running, telnetd will display the contents of the file /etc/issue. After login is completed, the most common delay is due to quotas being enabled. And if you have NFS running on your server (specifically: filesystems from other computers), then delays will be common and excessive. Even if you run quotaoff on all the filesystems, the login program will check every mounted filesystem including NFS for the existence of a quotas file. If the command:

bdf

is slow or hangs, then you have NFS problems that need to be fixed.

Re: telnet problem

radi_1 — Tue, 28 Nov 2006 02:06:53 GMT

Dear all,
I checked the following:
-quota is off
-ping is ok(zero packets lost & no delay)
-no nfs exported or imported
-bdf response is normal

but I noteced a strange thing with the tty's through which telnet is performed,there are certain /dev/pts devices
recieves the login: prompt quickly & the login proccess is fast,for example(/dev/pts/t1 or t2 or t3 but not t16 or t18).
Any idea?