Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!genrad!decvax!ucbvax!UTAH-CS.ARPA!cetron%utah-ced
From: cetron%utah-ced@UTAH-CS.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: re: vaxnet and yfdriver
Message-ID: <8702161636.AA00747@utah-ced.ARPA>
Date: Mon, 16-Feb-87 11:36:56 EST
Article-I.D.: utah-ced.8702161636.AA00747
Posted: Mon Feb 16 11:36:56 1987
Date-Received: Tue, 17-Feb-87 06:09:59 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: info-vax@sri-kl.arpa


I have no idea what the problem might be but I can suggest a course of action:

1. try using the same 1200 baud port with KERMIT or set host/dte   to determine
	if this is a yfdriver/terminal port/modem problem or specific to vaxnet.

2. if the above doesn't work, then try the 9600 port at 1200 baud to determine
	if you have a bad port, or it is the modem on the 1200 baud port.

3. if #1 works, then vaxnet is the culprit.  Try calling Robin Miller (?) at 
northern telecom ( I believe he is the author, if not call the correct author)

-ed cetron