Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!blake!ogccse!fosterm
From: fosterm@ogccse.ogc.edu (Mark Foster)
Newsgroups: comp.dcom.lans
Subject: Re: null Ethernet
Message-ID: <1987@ogccse.ogc.edu>
Date: 10 Feb 89 09:40:36 GMT
References: <1064@wasatch.UUCP> <27748@bu-cs.BU.EDU> <1070@wasatch.UUCP>
Reply-To: fosterm@cse.ogc.edu (Mark Foster)
Organization: Oregon Graduate Center, Beaverton, OR
Lines: 29

In article <27748@bu-cs.BU.EDU> kwe@buit13.bu.edu (Kent England):
>
>	Someone reported flaky behaviour using this product as a null
>modem.
Yeah.  We had severe problems with them when they were used (get this)
with both ports connected!  ANC sent a nice note recalling certain
serial nr.s.  They happily exchanged ours but the behavior was
the same (lots of jamming and dropped packets during activity
on both ports).  I now use them for "hot spares" for our single
port transceivers, when needed.

In article <1070@wasatch.UUCP> haas@cs.utah.edu (Walt Haas):
> but the phone number there has been disconnected
>(although directory assistance still give it out).  Does anybody know
>what's going on with these guys?

I suspect that they couldn't get their product problems resolved,
and being a young startup, dissolved quietly.

Like Kent said, the cost-effectiveness using ANC's solution was 
dubious at best.  I'd go with wiring a couple Cabletron transceivers
together for the cheapest, most reliable solution.

----
Mark Foster
CSE Systems Support
Oregon Graduate Center
Beaverton, OR
    fosterm@cse.ogc.edu