Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!FNALB.BITNET!WARNER..NAGY
From: WARNER..NAGY@FNALB.BITNET (Frank.J.Nagy@jade.Berkeley.EDU,
        VAX Wizard & Guru)
Newsgroups: comp.os.vms
Subject: RE: DECServer and DECnet incompatibility??
Message-ID: <8712250035.AA24175@jade.berkeley.edu>
Date: 23 Dec 87 13:59:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26

Leo Geoffrion <MANAGER%SKIDMORE.BITNET@CUNYVM.CUNY.EDU> writes:

> Some internal DEC documentation for the DECserver 500 suggest that it may
> be incompatible with asynchronous DECnet.  In other words, if you intend
> to use asynchronous DECnet to connect to micros with either DECnet DOS or
> TSSnet (for the Mac's), then you cannot use a Terminal Server for your
> communication port.

> Is it indeed impossible to connect asynchronous DECnet on top of LAT-11?
> Has anyone seen a work-around for this?  I'd really hate to have to go back
> to reinstalling our old DZ-11's.

This might well be true.  However, you might want to look into another
Digital product, the DECRouter-200 (I think its -200 and not -100), this
is a box based upon the DECServer-200 (8 lines) which becomes a DECnet
router box on the Ethernet and provides up to 8 asynchronous DECnet
connections for PCs, etc.  In other words, this does exactly what you
want it too and, since the DECRouter is self-contained, does not impose
additional load on your host VAXes to handle the async DECnet connections.


= Frank J. Nagy   "VAX Guru & Wizard"
= Fermilab Research Division EED/Controls
= HEPNET: WARNER::NAGY (43198::NAGY) or FNAL::NAGY (43009::NAGY)
= BitNet: NAGY@FNAL
= USnail: Fermilab POB 500 MS/220 Batavia, IL 60510