Code: Select all
NOTE: IP adresses are examples and need to be adopted according to local config
Windows: ipconfig -> find IP address if VMnet8 adapter -> 192.168.199.1
VMware Workstation Player: -> configure network interface as NAT (VMnet8)
OpenVMS x86-64:
@TCPIP$CONFIG
-> Optional components -> configure PWIP
-> Core components -> domain -> same as used in company intranet
-> Core components -> interfaces -> 192.168.199.192/24
-> Core components -> routing -> 192.168.199.2 (.2 is important)
-> BIND resolver -> configure DNS servers from company intranet
@NET$CONFIGURE -> Directory services to use: local,domain
LOCAL: LOCAL:.nodenm
DNS/BIND: nodenm.domain
Test DECnet-over-IP locally with $ SET HOST localhost
Start VPN to company intranet and wait a minute...
$ TCPIP PING some-node-in-company-intranet
$ TELNET x.x.x.x (IP address of some OpenVMS server in company intranet)
$ SET HOST IP$x.x.x.x (IP address of some OpenVMS server with DECnet-over-IP)
$ SET HOST FQDN-of-VMS-server-with-DECnet-over-IP
You now can transparently access the OpenVMS servers in the company intranet,
which have been configured to use DECnet-over-IP with all possible OpenVMS
x86-64 tools, which use RMS-based file access.
You can also define DECnet proxies on those OpenVMS servers:
UAF> ADD/PROXY IP$192.168.201.1::user local_user [/DEFAULT]
192.168.201.1 is the IP address of the 'PPP-Adapter VPN-xxx' adapter on your
Windows system.
Configuring access FROM the company intranet TO the OpenVMS x86-64 system
running at home on VMware Workstation Player requires a PRO license, to be able
to use the VMware Virtual Network Editor to define port mapping on the VMnet8
adapter
Volker.