DECnet crashed the system

[arpadffy]

> ... but cannot reach any other nodes on the network.

"cannot" is not a useful problem description.

Also, the non-psychics in your audience might know very little about
your "any other nodes" or your "the network".

Thank you for the response... and you (sms) are absolutely right that I haven't specified the environment.

I run DECNet on a LAN segment on OpenVMS (VAX, Alpha and IA64), Tru64 (Alpha), Ultrix (VAX) and Debian and Ubuntu servers (x86).
They all work very well.

From the X86VMS host all TCPIP operations works well... with the DECnet fail.

Code: Select all

$ set h 1.6
 Interrupt

$ set h 192.168.10.2
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable

while TCPIP works
$ telnet 192.168.10.2
%TELNET-I-TRYING, Trying ... 192.168.10.2
%TELNET-I-SESSION, Session 01, host 192.168.10.2, port 23
-TELNET-I-ESCAPE, Escape character is ^]

OpenVMS (TM) VAX Operating System, Version V7.3
VAX 4000-106A (KA56-A)
Welcome to VAX ...member of polarhome.com realm

...also DECnet on localhost works
Username:
$ set h 0

 Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-1

Username: system
Password:

I guess the issue is related to Windows 11 as described and analysed in viewtopic.php?f=9&t=8688

I have opened the TCP ports 102, 399 on the firewall... but nothing helped.

I am shame... - as I am not a Windows user, but this was the only computer around that was able to satisfy the XSAVE CPU instruction requirement.

Thank you very much for all help... I'll live with TCPIP only for a while... in hope that soon I will obtain some other hardware capable of running this VM on Linux.

Regards,
Z

[cct]

Note that you can set the up the TCP/IP hosts database using TCPIP SET HOST command
See $ tcpip help set host

For DECNET you can use the DECNET_REGISTER to register other nodes. Make sure you get the details from the otyhe nodes first:

$ mcr DECNET_REGISTER

Chris

[sms]

Code: Select all

> I run DECNet on a LAN segment on OpenVMS (VAX, Alpha and IA64), [...]

   Ok, but _which_ DECnet?  If only IP is getting through to your VM,
then I wouldn't expect Phase IV DECnet to do the job.  Note that the
SIMH VAX in the example above runs:

>           Name = Compaq DECnet-Plus for OpenVMS ,

The IA64 system is similar:

          [
          Name = OpenVMS I64 ,
          Version = "V8.4-2L3"
          ] ,
          [
          Name = HP DECnet-Plus for OpenVMS ,
          Version = "V8.4-K  8-APR-2020 21:00:41.51"
          ]

> [...]  I'll live with TCPIP only for a while... [...]

   My point is that with DECnet-Plus, IP should be enough for DECnet.


> Note that you can set the up the TCP/IP hosts database using TCPIP SET
> HOST command [...]

   Or you could run a DNS server.  Around here, for example, instead of:

> ITS $ set ho 10.0.4.32

I could have done:

ITS $ set host wisp.antinode.info

      I'm WISP.  Who are you?
[...]

because:

ITS $ nslookup wisp
Server:  its.antinode.info
Address:  10.0.0.140

Name:    wisp.ANTINODE.INFO
Address:  10.0.4.32

   Or, thanks to DECNET_REGISTER, instead of:

> ITS $ set host 1.32

I could have done:

ITS $ set host LOCAL:.wisp
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable

   In fact, specifying just plain "wisp" also works:

ITS $ set host wisp

      I'm WISP.  Who are you?
 [...]

   I'm too ignorant about DECnet-Plus name resolution to say exactly
why it uses DNS in that case, but, whatever the details, I do find it
handy.