Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site fortune.UUCP
Path: utzoo!linus!security!genrad!grkermit!masscomp!clyde!ihnp4!fortune!rpw3
From: rpw3@fortune.UUCP
Newsgroups: net.lan
Subject: Re: Interlan LAN Equipment - (nf)
Message-ID: <1965@fortune.UUCP>
Date: Wed, 14-Dec-83 07:03:12 EST
Article-I.D.: fortune.1965
Posted: Wed Dec 14 07:03:12 1983
Date-Received: Fri, 16-Dec-83 01:46:56 EST
Sender: notes@fortune.UUCP
Organization: Fortune Systems, Redwood City, CA
Lines: 28

#R:asgb:-43200:fortune:5900003:000:1220
fortune!rpw3    Dec 14 02:00:00 1983

Be warned that currently (although it may change in the future), Interlan
is NOT publishing the protocols of their Terminal Server, so you can NOT
connect an NTS-10 on one end to any old Ethernet controller on the other
(not even one of theirs). The terminal servers can (presently) ONLY talk
to other NTS-10 terminal servers. So in effect, while cooperatively
sharing cable bandwidth with others, the NTS-10 is an async-to-async
stat/mux (albeit a good one).

It's a nice looking box, I just wish that a company that advertises their
"open architecture" so much wouldn't try this kind of "buy it all from us"
thingy. And when they get around to letting us know how to use it, I am
sure we will all like it, what with the multiple open connections and stuff.
(We gave them a lot of flak at a recent seminar at a local hotel, so they
know that at least a few people are upset.)

To repeat, even if you currently own an Interlan E-net controller on your
VAX or other machine, you will have to use async ports to talk to your
host-end NTS-10 (for now).

Rob Warnock

UUCP:	{sri-unix,amd70,hpda,harpo,ihnp4,allegra}!fortune!rpw3
DDD:	(415)595-8444
USPS:	Fortune Systems Corp, 101 Twin Dolphins Drive, Redwood City, CA 94065