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
Path: utzoo!decvax!decwrl!ucbvax!info-vax
From: Provan@LLL-MFE.ARPA
Newsgroups: mod.computers.vax
Subject: still no DECnet answer
Message-ID: <8512171235.AA14692@ucbvax.berkeley.edu>
Date: Mon, 16-Dec-85 12:56:00 EST
Article-I.D.: ucbvax.8512171235.AA14692
Posted: Mon Dec 16 12:56:00 1985
Date-Received: Wed, 18-Dec-85 00:41:37 EST
Sender: serge@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: info-vax@sri-kl.arpa


so far i've gotten two good guesses at my DECnet problem, but neither
panned out.

the first suggested the "set executor" command in StartNet was not
getting executed, thinking that perhaps i wasn't using StartNet.  Well,
i am using StartNet, and an additional "set executor state on" command
to NCP did not bring up the network anyway.

the second guess was that i forgot the "state on" parameters to the
define line and circuit commands.  since i did forget those parameters
a few times in my efforts to get the network up, i thought this was the
answer until i realized that i used the NetConfig command procedure for
the defines, i didn't do them myself.  sure enough, the permanent
database showed the states "on".

so i'm still out of luck.  can someone who's brought up Decnet on uVMS
with an ethernet confirm that they aren't having this problem?  i get
real suspicious when i follow the instructions exactly and it doesn't
work.  what could i possibly do wrong?
						provan@lll-mfe.arpa