Using Multiplicity via VPN?

from Stardock Forums

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 this board that mention possibly using a 2nd NIC or a USB ethernet adapter to get a 2nd IP address which Multiplicity can use.


Has this worked for people?  Is it fairly straightforward to set up?  And will Multiplicity work fine if it is not using the first interface defined/listed?


Cheers,


Tim


 


 
multiplicity
9,670 views 4 replies
Reply #1 from WinCustomize Forums Top
My laptop is almost always VPN'd to the office.
I did no special configuratin to use MP Pro on that laptop as a secondry.
MP is tied to the IP of the NIC. The VPN has it's own IP that does it's own thing.
Reply #2 from Stardock Forums Top

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 ...".
Object Desktop - Get all of our enhancement utilities in one suite
Reply #3 from WinCustomize Forums Top
I can't find anything like spit tunneling in my VPN config.

Advise me where to look and I will.

Posted via WinCustomize Browser/Stardock Central
Reply #4 from Stardock Forums Top

timbur, adding a second nic or using firewire for MP communications is very easy. My secondary machine has two Gb NICs connected to my LAN and I use the firewire as the interface for MP communications. All works just fine.


On a side not, you said that you can't use split tunneling; what does it have to do with MP? You shouldn't have any problem communicating with you local PCs even while connected through VPN because the VPN interface is a "virtual" one briding over you physical nic, which leaves your physical NIC also available for internal communications within your home network.


The only thing is that if you use the Microsoft builtin vpn client and need to send packets over a gateway (ie to go on the Web), if "Use default gateway on remote network" is checked, then you won't use your home Internet connection but will rather be redirected to the gateway to which your vpn connection points to. Unchecking it mean you'll be able to go on the web from your personal Internet connection and still be able to communicate with your corporate network.


One important thing to note though, it's that splitting connections isn't very secure, unless you use a firewall on your laptop that can protect against the security hole it creates between you local Internet connection and you vpn tunnel that points to your corp network. That's why some 3rd party or vendors vpn clients won't allow such setting. But with Microsoft builtin client, you should be able to do it easily, unless you are tied to some group policies that restrict this (which many admins don't really enforce anyway, for practical reasons).


Hope this help.