On Friday, April 17, 2020 at 1:58:22 PM UTC-4,
s.c...@ieee.org wrote:
> On Friday, April 17, 2020 at 9:33:37 AM UTC-4, Tom Adams wrote:
> > On Saturday, April 4, 2020 at 8:54:28 AM UTC-4, Volker Halle wrote:
> > > Tom,
> > >
> > > can you ping the laptop IP address from OpenVMS running in your FreeAXP instance ? And vice versa ? If so, you should be all set…
> > >
> > > Start your X-Server on your laptop and issue the following in your OpenVMS system:
> > >
> > > $ SET DISPLAY/CREATE/NODE=ip.address.of.laptop/TRANSPORT=TCPIP
> > >
> > > Then test X-Windows with:
> > >
> > > $ RUN DECW$EXAMPLES:ICO
> > >
> > > you should get a rotating 'thing' on your laptop's X-Windows display.
> > >
> > > Volker.
> >
> > The problem is that I can't get the ping. I am stuck at that point. I can't find a configuration that provides a working network for the virtual vms system.
>
> Does the hardwired NIC have an IP address assigned it it? You can find this out from the command interface c:\ ipconfig
>
> C:\Users\Steve>ipconfig
>
> Windows IP Configuration
>
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Link-local IPv6 Address . . . . . : fe80::c7a:b8cc:
> IPv4 Address. . . . . . . . . . . : 192.168.x.x
> Subnet Mask . . . . . . . . . . . : 255.255.x.x
> Default Gateway . . . . . . . . . : 192.168.x.x
>
> If it does have an IP address can you ping the address from the windows machine/from another windows machine?
>
> If you can verify that the Windows box can communicate through that interface (NIC) then take the next steps to connect up the virtual nic with a bridge and the appropriate settings for the nics.
>
> I apologize if this is too simple/redundant for you but I'm taking you at your word that you don't have a lot of networking experience.
Nothing is to simple for me. I think I did that exercise. I tried to follow the advice in the Virtual Alpha's User Guide for Avanti version Version 2.6 (2015). It was in section 10.3:
10.3 NETWORKING AVANTI ON A SYSTEM WITH A SINGLE NIC Assigning Avanti its own NIC on a single NIC host system is feasible using a virtual NIC. OpenVPN is one way to create a virtual NIC under Windows. The following steps describe how to create a virtual NIC using OpenVPN 2.1.1: Assigning Avanti its own NIC on a single NIC host system is feasible using a virtual NIC. OpenVPN is one way to create a virtual NIC under Windows. The following steps describe how to create a virtual NIC using OpenVPN 2.1.1:
1) Download the OpenVPN 2.1.1 installation package for Windows from
http://openvpn.net/index.php/open-source/downloads.html 1) Download the OpenVPN 2.1.1 installation package for Windows from
http://openvpn.net/index.php/open-source/downloads.html
2) Run the installation package, selecting only the “TAP Virtual Ethernet Adapter”.
3) Refresh the system's Network Properties. A new network connection with “TAP-Win32 Adapter V9” as the description should now be available. Rename this virtual adapter to “Avanti NIC”.
4) Go to the virtual “Avanti NIC” properties; choose “Configure”; and on the “Advanced” tab, set “Media Status” to “Always Connected”.
5) Select both the physical NIC that is connected to the outside world and the virtual “Avanti NIC”, right click, and choose “Bridge connections”.
6) From a cmd window, run “NET STOP MSIPCAP” followed by “NET START MSIPCAP” to restart the Avanti PCAP driver.
7) Run the Avanti configuration utility and choose the virtual “Avanti NIC” as the network adapter. This configuration allows the creation of network connections between the virtual Alpha, the host system, and the external network
I did this on a Windows 10 system using the ethernet card that was wired to communicate with my home router. I could ping the card via another windows computer. After I added it to the virtual bridge, I could ping the bridge but not the card (if I recall correctly, I could redo the experiment easily).
But I did not use ipconfig to look at the card address. I used the windows Network and Internet Settings > View your network properties. (Also can see it when you go to change adapter settings.)
I could never get this to approach to work.
(BTW, later I decided that my systems don;t count as single nic systems since they also have wifi. But, I am not sure of this, and I not sure if it matters.)
PS: If I at all sound like I know anything about Windows networking, it is only because I have been mucking around for the last week trying to solve this problem and always failing. Constant failure does not build one's confidence that they know what they are doing.