Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.berkeley.edu.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!ucbvax.berkeley.edu!info-vax
From: garry@LASSPVAX.TN.CORNELL.EDU (Garry Wiegand)
Newsgroups: mod.computers.vax
Subject: Re: Aynchronous decnet troubles
Message-ID: <8601242318.AA04535@lasspvax.tn.cornell.edu>
Date: Fri, 24-Jan-86 18:18:49 EST
Article-I.D.: lasspvax.8601242318.AA04535
Posted: Fri Jan 24 18:18:49 1986
Date-Received: Sun, 26-Jan-86 17:14:16 EST
References: <8601170721.AA28452@vax135.UUCP>
Sender: daemon@ucbvax.berkeley.edu.BERKELEY.EDU
Organization: Cornell Engineering && Flying Moose Graphics
Lines: 14
Approved: info-vax@sri-kl.arpa

Just a quick note: we also had trouble getting asynchrounous decnet (decnet
through a terminal line) up and running. Ours had multiplexers and leased
phone lines in the way to make it more interesting.

What finally made it "come alive" was switching the vax/750 end of the wire
from a DZ-11 port (TTxx) to a DMF port (TXxx). 

After a period of confusion, you may also have to SET TERM/PROTO=NONE and 
SET HOST/DTE link-line:  on both ends to let the bytes flush out.

garry wiegand
garry@batcomputer.tn.cornell.edu

PS - DEC should consider building error messages into DECnet someday :-)