Profile photo of bucks

Hi Rene,

For a time we used 2 nics per machine, and ran into the sort of problems you are describing.

The issue is quite technical, but to cut a long story short the code we use to discover other A&H products on the local network is probably sending broadcast traffic out of your 192.168.0.x nic.

This I believe is because we ask the system for a broadcast socket, and this will be bound to which ever nic your system considers to be eth0 (primary).

You have some choices, you can either type the IP address of the target Mixrack into the text box in the connections screen in Editor. The O/S should then choose the correct nic to communicate on based on the I/P and subnet mask.

Or if your running windows (XP in my example), you can invert the primary nic, by going to Control Panel, then Network Connections, then Advanced, Advanced Settings, then there is a box which says “Connections are listed in the order in which they are accessed by network services”, you can then invert your primary and secondary nics.

Note this may affect other network services on your machine, so its worth checking after making this change.

Your other option would be to change the IP settings of the Mixrack onto 192.168.0.xx so its alligned with your primary nic’s IP address / subnet mask.

Hope this helps,