Telnet Problem

[Tim Lim Paul C Alex D]

Hi,

We are experiencing poor response times when running our application over a telnet session. The first screen of the application normally is drawn instantly, but when using telnet, fo some reason the screen appears to be very fragmented and takes about 3 seconds to draw 5 lines. However, when using rlogin, the application behaves normally. I do not know what could be causing this. I am desparate for some answers / theories on this issue.
Thanks in advance.

Running on HP-UX 11.00

Regards

Alex

[Piotr Bronisz]

Hi
Check reverse resolving, i.e.
nslookup ip_address
Rgds
Piotr

[Tim Lim Paul C Alex D]

Piotr,

Thank you for repling to my posting. Unfortunately I need some help with your reply. When you suggest to look at reverse nslookup, what exactly should I be looking for. Are you suggesting that perhaps my telnet packets are being sent "all around the world" before they actully get to me ?
Thanks again.

Alex

[KapilRaj]

Hi ,

Are you using a terminal emulator software to do a telnet ?. If not, can you try with the same. This perhaps will solve your problem. You can easily download a trial version from net.

Best of luck

kaps

[Peter Van Sant]

Hi,

If you're having dns problems they would show up as a delay in getting the login prompt while
dns was trying to reverse lookup your IP.

In this case that does not appear to be the problem. I'd try two things.

Telnet localhost and see if it runs any faster when the client and server are the same box.

Look at any other scripts that run during login; .profile, .login, etc. that might be
getting in the way.

[Vincenzo Restuccia]

in your $HOME/.profile and $HOME/.login
add export TERM=hp,If you're running a c-shell (csh), type the following:
setenv TERM hp

[KapilRaj]

Hi friend,

My other friends are looking into the networking side fine. let them proceed, but i would like to bring some points into your notice from Unix side,

Once you login to through telnet and say ps you can find out that the Parent process id of your shell is telnetd. This does mean that the shell takes enviromental variables from telnetd which is his parent and your commands do take it from shell. so it's a chain.

Same with rlogin


I will give you one suggession

telnet to the server
stty -a > /tmp/telnet.stty
logout

now rlogin to the server
stty -a > /tmp/rlogin.stty

now see the diff

diff telnet.stty rlogin.stty > diff.stty
more diff.stty

There are some differences is'nt it ? . I think that's the issue.

The environmental variables which telnet gives you are not enough / suitable for your application.

Try & Get back

kaps

[Tim Lim Paul C Alex D]

Hello to all,
Thank you to all that responded to my posting. It is the first that I used this forum and have been happily surprised with the response I have received.
The issue we are having has been resolved. It appears to be HP's modifications they made to the TCP/IP stack for versions 10.30 and greater (11.00) They moved to a streams based stack that increased the speed of the stack substantially, however, the changes affected the operation of telnet over a WAN link. To overcome this, telnetd has some "hidden" ( I call use the term hidden, because I did not see these switches in the man pages ) switches that addressed these problems So, basically we needed to make a change in the /etc/inetd.conf file where the telnet daemon is being initialized :

FROM
telnet stream tcp nowait root /usr/lbin/telnetd telnetd

TO
telnet stream tcp nowait root /usr/lbin/telnetd telnetd -TCP_DELAY

The -TCP_DELAY switch solved all our problems.

For any of you interested, I have attached the telnetd document from the HP-UX 11.00 release notes :