telnet login delay

[송상후_1]

when we use telnet for login, after we have below message, we have some delay time about 3 or 5 minutes. After then we can login to the system.

Trying...
Connected to 88.10.1.150.
Escape character is '^]'.

So, for tracking, I used "inetd -b", below message is a part of syslog.

Nov 8 09:51:43 race inetd[1061]: About to select()...

Nov 8 09:51:48 race inetd[1061]: About to search servtab list for service

Nov 8 09:51:48 race inetd[1061]: Checking instl_boots/udp

Nov 8 09:51:48 race inetd[1061]: Checking recserv/tcp

Nov 8 09:51:48 race inetd[1061]: Checking telnet/tcp

Nov 8 09:51:48 race inetd[1061]: About to accept for SOCK_STREAM - telnet/tcp

Nov 8 09:51:48 race inetd[1061]: Accepted for telnet/tcp: ret=4

Nov 8 09:51:48 race inetd[1061]: About to getremotenames()

Nov 8 09:51:48 race inetd[1061]: About to inetd_secure()
** we have until this as above message "..Escape character is '^]'..."

Nov 8 09:53:08 race inetd[1061]: About to check secflag

Nov 8 09:53:08 race inetd[1061]: Inside dofork

Nov 8 09:53:08 race inetd[1061]: About to fork

Nov 8 09:53:08 race inetd[1061]: fork returned = 17191

Nov 8 09:53:08 race inetd[1061]: Doing sigsetmask(0L);

Nov 8 09:53:08 race inetd[17191]: fork returned = 0

Nov 8 09:53:08 race inetd[1061]: Waited for STREAM sock, getting ret code

Nov 8 09:53:08 race inetd[17191]: Pid=0, child

Nov 8 09:53:08 race inetd[1061]: Got ret code=0

Nov 8 09:53:08 race inetd[17191]: Child becoming leader

Nov 8 09:53:08 race inetd[1061]: Entered for(;;) loop.

Nov 8 09:53:08 race inetd[1061]: About to select()...

Nov 8 09:53:08 race inetd[17191]: resetsignals() called...resetting to SIG_DFL

Nov 8 09:53:08 race inetd[17191]: Child getting stuff

Nov 8 09:53:08 race inetd[17191]: Child got stuff

Nov 8 09:53:08 race inetd[17191]: 2. About to execl(/usr/lbin/telnetd,@)

[Sridhar Bhaskarla]

Hi,

This is clearly a 'name resolution' issue. Check your /etc/resolv.conf file and see the nameservers specified there are responding. Once you are in the system, try 'nslookup ' and see if you get a quick response. You may need to fix the entries in that file as well nsswitch.conf under /etc directory.

-Sri

[Steven E. Protter]

A good test of the DNS issues is thus:

telnet hostname

should take 3-5 minutes


telnet ip_address

should be instant.

Common cause is that the DNS server is slow, lagging. Microsoft DNS servers sometimes do this when improperly patched.

SEP

[Yogeeraj_1]

hi,

can you check what happens if you hardcode the IP address of the client in /etc/hosts.

regards
Yogeeraj

[R. Sri Ram Kishore_1]

Hi,

Take a look at these threads:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=90090
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=246754
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=91892

HTH.

Regards,
Sri Ram

[Gerhard Roets]

In General for long telnet logins check your name resolution.

If it is correct in /etc/resolv.conf, check that your /etc/nsswitch.conf, else check both.

The above entries points at the same thing. The machine need to do a reverse host lookup of you IP to see if its listed in inetd.sec

Regards
Gerhard