Xref: utzoo comp.protocols.tcp-ip:4910 comp.unix.aux:447
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!iuvax!rutgers!rochester!pt.cs.cmu.edu!cadre!sean
From: sean@cadre.dsl.PITTSBURGH.EDU (Sean McLinden)
Newsgroups: comp.protocols.tcp-ip,comp.unix.aux
Subject: Re: tcp-ip terminal servers
Keywords: terminal server tcp ip
Message-ID: <1625@cadre.dsl.PITTSBURGH.EDU>
Date: 18 Oct 88 21:48:50 GMT
References: <337@thor.wright.EDU> <417@wasatch.UUCP>
Reply-To: sean@cadre.dsl.pittsburgh.edu (Sean McLinden)
Organization: Decision Systems Lab., Univ. of Pittsburgh, PA.
Lines: 19

In article <417@wasatch.UUCP> haas@wasatch.UUCP (Walt Haas) writes:
>Right now I have a Micom/Interlan NTS-100 downstairs to evaluate.

Forget it! We have one of these (obtained from Black Box) and
the software is ancient. Their implementation of telnet is poor
and they don't support two way ports (which would allow you
to dial in or out). You have to disable the modem talk modes
because they interfere with the telnet protocol (when will
somebody fix this). Most of all, the support (which used to
be quite good with this company), really stinks.

What would be ideal is a server which had downloadable software
and a standard cpu (like a 68000), which would allow you to
write your own code and load it. That way you could support
SUPDUP, telnet, ROSE, or any old protocol that you like. In
the meantime, get LSI-11s and do it yourself.

Sean McLinden
Decision Systems Laboratory