Network issues with PersonalAlpha container

I am using a PersonalAlpha-created disk image which is using a network configuration that worked under PA. Using FreeAXP, there is no network device other than LO0 and I seem to recall that, somewhere, there was documentation of how to "convert" network settings as device names are different between the two emulators.

I am using a dedicated network device and can join a cluster successfully, but TCP/IP fails with the SE0: device and hence I have no TCP/IP.

Cheers

Gremlin,

FreeAXP emulates a DE500 LAN interface, which will show up as EWA0 under OpenVMS and as we0 in TCPIP.

Use @TCPIP$CONFIG -> 1 Core environment -> 2 Interfaces and configure we0

Volker.

Hi

That made no difference, but I went into LANCP, deleted SE0, added WE0, rebooted and then TCPIP$CONFIG found WE0.

However, still not working, probably because of my configuration....I am running FreeAXP under Windows2008 under Fusion for OSX!!! OSX is on a Mac Mini, therefore only a single network port. While this works fine for PersonalAlpha with their NDIS driver, it works poorly for FreeAXP. So, I added a USB/CAT5 converter which the VMware Windows can see and use, removed all bindings from it and configured it as the NIC for FreeAXP.

However, no network communication occurs through the device with VMS. If I enable TCP/IP and MS protocols again, the Windows host has no problems - so, am I going one step too far?

Hello Gremlin,

Just for clarification: you can join a cluster, but no TCP/IP from the emulator running under Fusion? If so, that's an indication that networking to the outside world is working.

Camiel.

Oops - double checked....the cluster join request is sent, but nothing happens. So, there is no network activity across the link by VMS.

Analysis indicates that Fusion sees the device (I can add it to a VM), the VM sees the device (I can give it an IP address within Windows and ping it, send/receive information using it and unbind all services/protocols from it), FreeAXP sees it (I can assign it as the network device for the emulator) and I think that OpenVMS sees it as I can see the device in SRM, change its mode to FastFD and within OpenVMS, I can do a show dev/fu EWA0 and it shows as a DE500.

Its just that no network traffic is moving across it!! If instead I use the MacMini inbuilt network card (bound to IP etc within Windows), I get network traffic in OpenVMS but it clashes with everything else - running dedicated is the way to go......if I can get it to work. Again, works seamlessly under PA.

Additional info:

On PA, there are two network devices, SEA0 (Lance device) and EWA0 - on FreeAXP there is no SEA0 device as nothing is bound to the network card in the Windows host. Could this be part of the problem? Recall, there are two NICs available in the host and I am dedicating one to FreeAXP with nothing bound to it.