Telnet sessions to our HP-UX 11.00 box "freeze" after about 30 seconds.
Nothing shows up in the syslog.  There's no securetty (I know it's a
Linux-ism, but that was my first thought...)  Where else can I look for
clues?

-- 
* John Oliver                              http://www.john-oliver.net/ *
* California gun owners - protect your rights and join the CRPA today! *
* http://www.crpa.org/         Free 3 month trial membership available *
* San Diego shooters come to http://groups.yahoo.com/group/sdshooting/ *

John Oliver <joliver@john-oliver.net> wrote:
> Telnet sessions to our HP-UX 11.00 box "freeze" after about 30
> seconds.  Nothing shows up in the syslog.  There's no securetty (I
> know it's a Linux-ism, but that was my first thought...)  Where else
> can I look for clues?

If you mean at the very beginning, you need to check your DNS
configuration and availability - HP-UX inetd/telnet will do a reverse
lookup of the client IP address.

If you mean pauses in the middle of an established telnet session,
start looking for packet losses - netstat -p tcp, then lanadmin, then
switch stats etc etc etc.

rick jones
-- 
denial, anger, bargaining, depression, acceptance, rebirth...
                                     where do you want to be today?
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to raj in cup.hp.com  but NOT BOTH...

> Telnet sessions to our HP-UX 11.00 box "freeze" after about 30 seconds.
> Nothing shows up in the syslog.  There's no securetty (I know it's a
Try with a minimal .profile. May be a command try to connect to something 
not responding.

John Oliver wrote:

> Telnet sessions to our HP-UX 11.00 box "freeze" after about 30 seconds.
> Nothing shows up in the syslog.  There's no securetty (I know it's a
> Linux-ism, but that was my first thought...)  Where else can I look for
> clues?

You can get an idea of which half of the world to look (this machine vs
the rest of the world) by trying a telnet to the local host loop back.
If that fails during the connection, check the DNS, if it fails after
the connection is established, its got to be in the local software.  If
it doesn't fail, then consider reliablility of the net.

Joe

On Fri, 15 Oct 2004 13:15:49 -0400, Joe Blow wrote:
> John Oliver wrote:
> 
>> Telnet sessions to our HP-UX 11.00 box "freeze" after about 30 seconds.
>> Nothing shows up in the syslog.  There's no securetty (I know it's a
>> Linux-ism, but that was my first thought...)  Where else can I look for
>> clues?
> 
> You can get an idea of which half of the world to look (this machine vs
> the rest of the world) by trying a telnet to the local host loop back.
> If that fails during the connection, check the DNS, if it fails after
> the connection is established, its got to be in the local software.  If
> it doesn't fail, then consider reliablility of the net.

Telneting to localhost works just fine.  DNS is working.  After messing
around a little more, it seems that, as long as I'm doing something, the
connection will stay up.  If I stop typing and hitting enter for more
than a few seconds, it "freezes".

I really doubt this is a network issue, as I can deal with every other
UNIX machine in that lab just fine.  It just about has to be a software
issue on the HP-UX machine, but... what?  Where would I look?  Is there
maybe a newer telnetd I should be using?  Some sort of PAM-like security
software?

-- 
* John Oliver                              http://www.john-oliver.net/ *
* California gun owners - protect your rights and join the CRPA today! *
* http://www.crpa.org/         Free 3 month trial membership available *
* San Diego shooters come to http://groups.yahoo.com/group/sdshooting/ *

John Oliver wrote:

> On Fri, 15 Oct 2004 13:15:49 -0400, Joe Blow wrote:
> 
>>John Oliver wrote:
>>
>>
>>>Telnet sessions to our HP-UX 11.00 box "freeze" after about 30 seconds.
>>>Nothing shows up in the syslog.  There's no securetty (I know it's a
>>>Linux-ism, but that was my first thought...)  Where else can I look for
>>>clues?
>>
>>You can get an idea of which half of the world to look (this machine vs
>>the rest of the world) by trying a telnet to the local host loop back.
>>If that fails during the connection, check the DNS, if it fails after
>>the connection is established, its got to be in the local software.  If
>>it doesn't fail, then consider reliablility of the net.
> 
> 
> Telneting to localhost works just fine.  DNS is working.  After messing
> around a little more, it seems that, as long as I'm doing something, the
> connection will stay up.  If I stop typing and hitting enter for more
> than a few seconds, it "freezes".
> 
> I really doubt this is a network issue, as I can deal with every other
> UNIX machine in that lab just fine.  It just about has to be a software
> issue on the HP-UX machine, but... what?  Where would I look?  Is there
> maybe a newer telnetd I should be using?  Some sort of PAM-like security
> software?
> 
what if you just run a small script to loop on the telnet session, does 
it still lock up? If it doesnt then it sound like a ttl issue with the 
telnet connection.