[HECnet] Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name:,PIPY (was Re: DECnet-VAX for VMS 2.0 Setup Question)

Hi Paul, I made some progress and need help with the next step - connecting to pydecnet. Current status is DECnet 1.3 is up on VAX/VMS 2.0, I can SET HOST to self, and have DMC11 XMA0 device up and a link to DECnet/Python configured. There is no way to avoid a receive password that I can figure out, so I am using HELLOVAX as both receive and transmit pw: CONFIGURATION DATABASE NODE PIPY NODE NUMBER: 32 PASSWORD REMOTE RECEIVES DURING INITIALIZATION: HELLOVAX PASSWORD REMOTE SENDS DURING INITIALIZATION: HELLOVAX SECONDARY LOADER FILE: TERTIARY LOADER FILE: DOWNLINE LOAD FILE: DEFAULT NON-PRIVILEGED USERID: GUEST DEFAULT NON-PRIVILEGED ACCOUNT NAME: DEFAULT PRIVILEGED USERID: SYSTEM DEFAULT PRIVILEGED ACCOUNT NAME: NSP CONNECT TIMEOUT CONSTANT 0 SECONDS REMOTES SERVER NODE: SERVERS LINE TO REMOTE: REMOTES HOST NODE: CONFIGURATION DATABASE LINE XMA0 DEVICE TYPE: DMC11 CONTROLLER NUMBER: 0 LINE NUMBER:0 LINE ADDRESS:0 ASSOCIATED NODE: PIPY ASSOCIATED BUFFER SIZE: 192 NUMBER OF BUFFERS TO ALLOCATE: 6 CHARACTERISTICS: FULLDUPLEX MOP TIMEOUT CONSTANT:  10 SECONDS pydecnet .ini has: circuit DDCMP-31-43 DDCMP tcp:31431:172.31.31.31:31430 --t3=15 --cost=4 node 31.43 XX --inbound-verification HELLOVAX --outbound-verification HELLOVAX and I keep getting OPCOM messages on the VAX saying: *   Opcom, 03:17:09.56, NETACP       Accnt=    Opcom, DECnet line XMA0: INIT message protocol error from address: 32, name: PIPY * I must be very close to getting 31.43 (XX) in if Phase II is supported like you indicated ... Anyway, advice for me please? Best regards Supratim  STATUS OF LINE, AS OF 26-SEP-2022 03:13:57.44         LINE-ID                 STATE                   REMOTE         DMC11_0                 OFF                     PIPY On 9/25/22 12:51 PM, Johnny Billquist wrote: --