I've followed the instructions in the release notes (for working with a single NIC and with a wireless card) and have got to the stage where both my host laptop and emulated Alpha can ping my router but they cannot ping each other.
They can also both ping another machine on my network (and I can telnet into the Alpha from here).
What have I missed?
Host - HP/Compaq nc8430 (dual core), XP Pro, 3GB. My network is wireless.
Emulated Alpha - VMS v7.3-2 (unpatched), UCX v5.4, DECnet not configured.
Go to the hardware NIC in network properties and uncheck all options under the General tab, this connection uses the following items:. Then be sure the hardware NIC is assigned to FreeAXP in the configuration Wizard and reboot the emulator.
What's probably happening is Windows is still using the hardware NIC as it's primary NIC. Hence your telnet is running on the same NIC as the emulator. Disabling TCP/IP on the hardware NIC will force Windows to use the wireless NIC.
The same problem can occur on a system with dual NICs. Be sure the NIC assigned to FreeAXP has TCP/IP disabled in the NIC properties. Unchecking all options for the FreeAXP NIC guaranties the emulator has exclusive access to the device.
I'll post an update in the Release Notes. This is also covered in section 4.1 in the User Guide.
I tried your suggestion without success - But I did find a solution...
I have configured the network bridge (as recommended in the release notes). Only on the bridged connection do I see the "This connection uses" menu. Unchecking all these meant that my PC could not see the outside world at all.
If I go to the wireless network connection, I don't see the "This connection uses" menu.
I tried unchecking various options and eventually ended up doing a reboot. Still no success.
So I put everything back as it was and found that the emulated system COULD ping the PC. But the PC could only PING the emulated system after the emulated system had PINGed it first.
So I thought the solution should be a very simple one - just add $ TCPIP PING <host system IP address> to SYSTARTUP_VMS.COM after TCPIP has been started.
But it's not quite that easy. That's fine ifsho you connect from the host to the emulated system within a few seconds of the PING but if you wait for a while, the PC seems to loose the route to the emulated system. (This happened in less than 2 but more that 1 minute on my system).
I tried playing with some of the TCP keepalives but without success. So Iíve put a batch job in place to PING the host interface every 60 secs.
Iím sure someone will be able to suggest a better way!
malmberg December 12 2017 HPE only makes the most current version of OpenVMS Alpha / IA64 /VAX available to hobbyists. When I had access to the Alliance 1 program it was the same. No public downloads are allowed by HPE.
nmbonao December 08 2017 Is anybody knows OpenVMS 8.2 version downloadable version? or CD copy? Thank you very much
aarommes December 02 2017 Bitcoin and Blockchain enthusiasts ( plus distributed computing ) please connec / reply: http://www.openvmshobbyis t.com/forum/viewthread.ph p?forum_id=130&thread_id= 2991
malmberg September 10 2017 https://sourceforge.net/p /vms-ports/wiki/VMSInstal lation/ For the most part just use VMS 6.1 media instead of 7.3. But why run the older release?
DoeveR August 07 2017 Where can I find the write up on running VMS 6.1 using the simh emulator?
Bart March 20 2017 Happy to have found my password again!