How to choose one of multiple networks

When I use the PC name MP always grabs the wireless and I want it to use the wired . . .  so I just use the IP address.

On a secondary Multiplicity will bind to all network interfaces.  On the primary it will use the best route (determined by the OS) to the specific IP.  If you are looking up by name and the secondary machine has two ips then it will pick the first one it can connect to.

If you want to specify an interface then you will have to do as Zubaz suggests and disable auto lookup and use the IP address instead.

There needs to be an override. Clearly the OS isn't choosing the best route on the primary machine. MP is binding to one subnet while the client is on a different subnet. If I were allowed to choose which network connection to always use, this problem would go away.

I've disabled auto-lookup and it still doesn't work reliably (most days it's OK, others it refuses to work). When I change the settings on the primary for the client, it appears to attempt to contact the client, which I assume it successfully does, since I don't get any error message. But, it refuses to actually connect. Sometimes the primary MP tray icon will flash on and off a few times, but then stay off.

Pinging by name or IP yields a solid connection.

The only piece that could be interfering is that I'm using Hamachi. MP on the primary is binding to the Hamachi connection, not the physical LAN connection. On the client, I have turned off Hamachi and so it's only binding to the physical LAN connection.

I read in another post that there should be a new beta this week...how do I get my hands on it to see if my issue goes away?

The beta can be downloaded via SDC.  Just enter your Multiplicity serial into it and make sure show betas is enabled.