LAT/Telnet gateway documentation omission
David C. White
davew at gvgpsa.GVG.TEK.COM
Thu Jul 27 10:54:45 AEST 1989
While setting up some LAT/Telnet gateway ttys, I found some an omission
in the documentation. I set everything up as specified and when I
tried to connect to the 'telnet' service, I got the 'insufficient node
resources' message. After putzing around with everything for a while I
decided to call the support center. If I tried to connect to the node
name I would end up getting the 'telnet>' prompt from the server.
I decided to give TFM another shot and looked at lcp some more and got
a clue from the 'v' and 'V' options. When I originally tried to set up
the LAT gateway, I used the first 4 LAT ttys. MISTAKE! The LAT ttys
must evidently be assigned in the order that the multiple services are
defined, i.e., since the host is usually defined as the first service,
the number of tty devices that you want for normal LAT service must be
the first LAT devices and the ttys assigned to the second defined
service must after these.
For example, if you have 16 LAT ttys, tty20-tty35, defined and you want
normal LAT connections through a server to your node and you want to
have 4 LAT ttys assigned to the lat/telnet service which is defined
second in the 'lcp' command, you would set up tty20-tty31 with the
standard '/etc/getty' command and then you would set up tty32-35 with
the '/usr/etc/lattelnet' command. If you get these in reverse order,
if you do a connect to the host service, you end up with the 'telnet>'
prompt, and if you try to connect to the service you have defined as
'telnet', you will get the insufficient node resources message.
[Just got a call back from the support center and they confirmed this]
My gripe is that this is not described in the documentation on setting
up the LAT/Telnet gateway service. I hope this helps someone that may
be attempting to do this.
The second problem I ran into, after I got everything working, is that
when you connect to the telnet service, before you do the 'open host'
command, the session is in interactive mode as it should be. After the
connection to the host is established, looking at the session shows
that it is now in passall mode. The support center is researching this
one since they didn't have a ready answer. Anyone else run across this
one, or I have missed something else?
This is with Ultrix 3.0 (still waiting on 3.1 which I was told had been
sent on its way to me on July 22) and a DECserver 200 with 2.0 software.
--
Dave White Grass Valley Group, Inc. VOICE: +1 916.478.3052
P.O. Box 1114 Grass Valley, CA 95945 FAX: +1 916.478.3778
Internet: davew at gvgpsa.gvg.tek.com UUCP: ...!tektronix!gvgpsa!davew
More information about the Comp.unix.ultrix
mailing list