timbur

I am in a similar boat, only I have no expectation of Multiplicity being able to work between my work PC connected via VPN and my home machines. The reason why is your work VPN, which does not allow you to communicate with your local non-work PCs. If it did, then this would be a security risk your corporate masters would not like. It's the same reason you aren't able to print to a local network printer or cannot browse files on your non-work PCs while connected to your VPN.<

Thanks, Zubaz. I wonder whether your VPN has Split Tunneling enabled, or something like that, which enables you to actually communicate to the LAN machines. Mine doesn't. If I can manage to ping machines on my LAN, then I will be OK. Currently I am seeing whether I can manage to do this using a "route delete ...".

I currently have just my work laptop and my main home PC on my desktop, but once I finish rearranging and putting up my new desk, I will be adding several new testbed PCs and other home servers to the mix. For my main home PC and those extra ones, I will likely try to use Multiplicity Pro. But I would also like to use Multiplicity on the work laptop, which is almost always connected to work via the VPN. I've seen a few posts on t