On Oct 20, 2022, at 06:43, Supratim Sanyal <supratim@riseup.net> wrote:
On 10/20/22 5:10 AM, Trevor Warwick wrote:
Should later VMS be able to talk to it ? It doesn't seem to work for me (VMS 5.4):I haven't been able to talk to it from VMS later than 3.5 either. CTERM and RTERM don't seem to find what they look for.
PRRSI$ set host 31787
%SYSTEM-F-CONNECFAIL, connect to network object timed-out or failed
If I try from VMS 7.3
KRAKAR$ set host /app=rterm 31787
%SYSTEM-F-LINKABORT, network partner aborted logical link
KRAKAR$ set host /app=cterm 31787
%SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
On Tue, 18 Oct 2022 at 22:40, Supratim Sanyal <supratim@riseup.net> wrote:
On 10/18/22 11:07 AM, Johnny Billquist wrote:
> Well, outbound to RSX also don't seem to work.
>
> Maybe you could do another trace when trying to connect from RSX to
> VMS? That might help me some more.
tcpdump attached (31.12=RSX, 31.43=VMS2.0, 31.32=pydecnet); here's what
RSX says - it tries "RMT" and fails. TOPS-10 uses "NRT" and succeeds.
>ncp
NCP>show node xx
Node summary as of 18-OCT-22 21:32:12
Remote Active Next
Node State Links Delay Circuit Node
31.43 (XX) 0 30 31.32 (PIPY)
NCP>exit
>set host xx
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Network access failure
_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se
_______________________________________________ HECnet mailing list -- hecnet@lists.dfupdate.se To unsubscribe send an email to hecnet-leave@lists.dfupdate.se--_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se