FreeAXP on VirtualBox Windows10 on OSX - NIC problem

Output received. Thanks. We'll have a look and see what we can figure out.

It looks like you have teamed the NICs. I see a Microsoft Network Adapter Multiplexor Driver with an IP assigned while the Intel(R) PRO/1000 MT Desktop Adapters have no IP assigned.

Try this. Remove the Multiplexor. Allow all Windows default network functions on one of the Intel NICs. Re-install FreeAXP to force a refresh of the NIC list. See if both Intel NICs show up in the configuration utility NIC list.

FYI: Once you can see the NICs, it is sometimes necessary to treat virtual NICs like a wireless NIC. See sections 10.9 and 10.7 in the User Guide.

I originally had the drives unbridged, as that didn't work, I found an article bout bridging them and trying to use the bridge adapter.

I have tried with both NICs in their default config, and one in default and the other with everything removed (MS client, IP4 and 6 etc.), but that didn't work either...

Ok, we shall continue our research.

[UPDATE]
The problem was almost certainly that the Windows installations were 32bit...even though I had "forced" a 64bit install.

So, I installed Windows Server 2016 64bit and - bingo - interface appears and can be configured.

And so now I have an additional/different problem...

The vAlpha has a fixed IP address of 192.168.56.10 on WE0 and it can ping itself and 127.0.0.1; the Windows host running on VirtualBox can also ping the VirtualBox LAN (vboxnet0) of 192.168.56.254 . The vAlpha can't ping any other IP address. Within the vAlpha, TCP is configured to use 192.168.56.254 as its router/gateway; there are no errors in startup.

The Windows host has two NICs, one is configured with all services (including TCPIP) unbound/unchecked and it is this NIC that is configured in FreeAXP as the DE500.

Clearly I am doing something wrong, but I can't figure out what it is...

Take a look at sections 10.7, 10.9, and 10.10 in the User Guide. Also, you say IPV4 is enabled on the Windows side of the NIC used by FreeAXP. Make sure the IP address assigned on the Windows side does not conflict with the 192.168.56.10 address used by the FreeAXP system.