Clustering FreeAXP - Personal Alpha

I managed once to build a 3 node cluster on a XP 32 bits running on a dual core laptop, using FreeAXP, Personal Alpha and ES40 (extremely slow but beautiful).
Whatever I did to make them see each other on the network, I don't know, it's not working anymore.
I'm trying now to make just a 2 nodes cluster using FreeAXP and Personal Alpha, bridging together 2 Loopback devices and 1 TAP-Win32 Adaptor V9. The bridge has IP 10.0.0.1 and VMS's have 10.0.0.2 and 10.0.0.3, all have mask 255.255.255.248. I chose this mask to avoid conflict with another subnet in the same class.
IF I start first FreeAXP, I can ping it and connect to it with telnet. When I start also Personal Alpha, I lose connection to FreeAXP but in exchange I can connect to P.Alpha. Obviously the VMS nodes don't see each other.
MAC addresses of VMS nodes are also different. I can't see where is the conflict.
IF I start first Personal Alpha, I never get a connection to FreeAXP.
What am I doing wrong?

What happens if you try the same set-up, but substitute a SimH VAX instance for PersonalAlpha?

Is the clustering using the new TCP/IP clustering?

Are the MAC addresses correct?

Are all the SCSSYSTEMID values correct and unique?

I am currently clustering FreeAXP and SimH, but have each on their own dedicated Virtual Box VM as documented in another thread.

@ Bruce and malmberg thanks for your replies but after many tries I found a solution. It appeared to me when I decided to ignore network guide from FreeAXP manual and use some basic logic instead. Apparently TAP adapter does not like bridging.
I just bridged 2 loopback adapters and assigned one loopback adapter to each emulator and it worked! I kept the same IP configuration as in my first post.