If on the Primary machine, you right click the Mult. icon, and go to configure. There's a list of your attached computers, Right click the one that changes i.p. addresses and choose configure.
There's an option here that says 'look up the i.p. address each time' This should cause Multiplicity to try and locate the machine before connecting, instead of making an assumption about it's i.p. address.
If it's not that, it's possibly a problem I'm about to add a post on; you can't really control what i.p. address multiplicity listens on, and when you have a VPN up & start Multiplicity, it probably configures itself to listen on the VPN interface, instead of your network. In this case, I'd suggest restarting the stardock service after you disconnect your VPN. To do this, go start > run > 'services.msc' and OK; Locate "stardock Multiplicity" and select it. There's a single button for stop start at the top of the screen that looks like []|> (stop / play) that should do the trick. Double click the mult. icon now, and check out the address at the top of the page (title bar)
Good luck!
I apologize for the delayed response (I had somehow overlooked your forum post).
You could use (P) and (S) for primary and secondary naming schemes. It would also help if you could initially specify which machine (desktop or laptop) is primary and which is secondary.
Which version of Windows (including service packs) are you running on your two machines?
What version of multiplicity are you using?
What vpn client and version are you using?
I've forwarded your issue to the development team.
-Mike
[Stardock Support]
Welcome Guest! Please take the time to register with us.
- Richer content, access to many features that are disabled for guests like commenting and posting on the forums.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!