RE: Dumb terminal connection

From: ALLEN, David (David.ALLEN_at_eur.crowncork.com)
Date: 05/26/04

Next message: Sabrina Lautier: "NIS: delay in passwd change"

Previous message: Venkatakrishna P.V: "Fw: Patch installtion on Soalris 7 SPARC."
Maybe in reply to: ALLEN, David: "Dumb terminal connection"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

To: sunmanagers@sunmanagers.org
Date: Wed, 26 May 2004 10:03:18 +0100

Thanks for all your helps and suggestions.

On further investigation, I think my description of a terminal server may
have been a bit misleading. True, it is a box into which plugs 8 terminals,
but communication with the server is via tcpip.

Consequently, the problem is more akin to one computer not being able to
telnet into another. Now this works OK from other SUNS or PC's so I can only
assume it is something to do with the age or version of the TCPIP used on
the terminal server. The snoop below shows basic communication between the
two devices, but obviously a full connection is not established.

Any suggestions? The only other comment I can make is that we have a another
2.6 box which I cannot connect to, which suggests at some time in the dim
and distant past I did this fix on our old server.

Thanks again for any comments.

David

-----Original Message-----
From: Moehlman, Mike [mailto:mmoehlman@txi.com]
Sent: Tuesday, May 25, 2004 5:16 PM
To: ALLEN, David
Subject: RE: Dumb terminal connection

Your snoop confirms that traffic is flowing in both directions. However, I
don't see the "login:" prompt being sent. There maybe some tcp setting that
need to be adjusted. I am not familiar with many options here.

I have only used snoop a few times to do some basic troubleshooting. There
are others on the list who really know how to use the tool. Here is a
sample from one of my Solaris 9 servers snooping a incoming telnet session
(although I am not using a terminal server for this connection).
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105 login:
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
172.16.11.19 -> 172.16.21.47 TELNET R port=4105
172.16.21.47 -> 172.16.11.19 TELNET C port=4105
...

-----Original Message-----
From: ALLEN, David [mailto:David.ALLEN@eur.crowncork.com]
Sent: Tuesday, May 25, 2004 10:10 AM
To: Moehlman, Mike
Cc: sunmanagers@sunmanagers.org
Subject: RE: Dumb terminal connection

Hi,

This is the output from the snoop command. I have know idea what is all
means as this is the upper edge of my knowledge! 104 is the terminal server,
and serva is the server. While the info below is being displayed, the
terminal is hanging. If it was working correctly, a login prompt would
appear.

snoop 6.52.9.104
Using device /dev/bge0 (promiscuous mode)
  6.52.9.104 -> 6.52.9.0 WHO R port=513
  6.52.9.104 -> 6.52.9.0 WHO R port=513
  6.52.9.104 -> 6.52.9.0 WHO R port=513
  6.52.9.104 -> serva TELNET C port=5015
       serva -> 6.52.9.104 TELNET R port=5015
  6.52.9.104 -> serva TELNET C port=5015
       serva -> 6.52.9.104 TELNET R port=5015
       serva -> 6.52.9.104 TELNET R port=5015
       serva -> 6.52.9.104 TELNET R port=5015
       serva -> 6.52.9.104 TELNET R port=5015
       serva -> 6.52.9.104 TELNET R port=5015
  6.52.9.104 -> 6.52.9.0 WHO R port=513
       serva -> 6.52.9.104 TELNET R port=5015
       serva -> 6.52.9.104 TELNET R port=5015
  6.52.9.104 -> 6.52.9.0 WHO R port=513
       serva -> 6.52.9.104 TELNET R port=5015
  6.52.9.104 -> serva TELNET C port=5016
       serva -> 6.52.9.104 TELNET R port=5016
  6.52.9.104 -> serva TELNET C port=5016
       serva -> 6.52.9.104 TELNET R port=5016
       serva -> 6.52.9.104 TELNET R port=5016
       serva -> 6.52.9.104 TELNET R port=5016
       serva -> 6.52.9.104 TELNET R port=5016
       serva -> 6.52.9.104 TELNET R port=5015
  6.52.9.104 -> serva TELNET C port=5015
  6.52.9.104 -> 6.52.9.0 WHO R port=513

Thanks again for your help.

David

-----Original Message-----
From: Moehlman, Mike [mailto:mmoehlman@txi.com]
Sent: Tuesday, May 25, 2004 3:01 PM
To: ALLEN, David
Subject: RE: Dumb terminal connection

Can you snoop packets coming from the terminal server when a connection is
being attempted? Any chance that the terminal server is trying to
automatically log in and not seeing an expected
"response/hostname/banner/...". Do the terminal server ports automatically
issue a connect or does the user have to type in "telnet host" or "connect
host"?

I would not expect transfer rates between the terminals and terminal server
to be an issue here.

-----Original Message-----
From: ALLEN, David [mailto:David.ALLEN@eur.crowncork.com]
Sent: Tuesday, May 25, 2004 8:38 AM
To: Moehlman, Mike
Cc: sunmanagers@sunmanagers.org
Subject: RE: Dumb terminal connection

Thanks for your reply.

The new box responds to ping requests and we can telnet into it from other
Suns/PC's etc so I don't think it is a routing/netmask problem. From the
new box we can also ping the terminal server. At the back of my mind, I
vaguely remember changing something to do with data transfer rates but I
cannot remember what.(it was five years ago!)

The Prime terminal server allows users to connect as a telnet session, and
if it was working, a who command at the console of the server would show the
user connected with the ip address of the terminal server. (I don't know if
this is the same with other makes of terminal servers?)

David

-----Original Message-----
From: Moehlman, Mike [mailto:mmoehlman@txi.com]
Sent: Tuesday, May 25, 2004 2:19 PM
To: ALLEN, David
Subject: RE: Dumb terminal connection

Assuming that the terminal servers are using telnet.

How can you connect to the new V250? Can you access it from the other 2.6
box? What IP class are you using (could it be a subnetting/routing
problem)? Does the new box respond ping requests? Is telnet disable via
inet.conf?

-----Original Message-----
From: ALLEN, David [mailto:David.ALLEN@eur.crowncork.com]
Sent: Tuesday, May 25, 2004 7:47 AM
To: sunmanagers@sunmanagers.org
Subject: Dumb terminal connection

Hi,

We recently replaced our E450 running Solaris2.6 with a V250 running Solaris
9, and all our dumb terminals which connect via terminal servers can no
longer connect. ie we cannot even get a login prompt. Logging into another
2.6 box from one of the dumb terminals still works.

The new machine is using the same ip address as the old one. Any ideas how
to regain connection?

Thanks in advance.

David

CONFIDENTIALITY NOTICE
The information contained in this e-mail is intended only for the
confidential use of the above named recipient. If you are not the intended
recipient or person responsible for delivering it to the intended recipient,
you have received this communication in error and must not distribute or
copy it. Please accept the sender's apologies, notify the sender
immediately by return e-mail and delete this communication. Thank you.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Next message: Sabrina Lautier: "NIS: delay in passwd change"

Previous message: Venkatakrishna P.V: "Fw: Patch installtion on Soalris 7 SPARC."
Maybe in reply to: ALLEN, David: "Dumb terminal connection"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]