VPN Connectivity Issues

Work arounds?

from Stardock Forums

Multiplicity is not working between my Main PC and Secondary while using VPN.

I know there are issues with using Multiplicity and some VPN systems.  This depends on how secure they setup the VPN system.

I've been using both for the past 8 months, but recently something has changed.  My work around for the past 8 months.  On my main PC, I created a Virtual PC, then used it to connect to my work's VPN system along with the laptop's also being connected to VPN.

Apparently within the past month, they changed the vpn system to not allow other desktops to talk with each other, while both are connected via vpn. (only a guess).

I can telnet to our hp box via my Primary PC.  Then use it to telet to my Main PC, and telnet to my secondary PC.  This seems to work fine.  I get the MULTIPLICITY2P from my Primary PC, and I get MULTIPLICITY2C98090 from my client.  Same with my client, I can telnet to the hp box, then telent using the muliplicity port number to both the client pc and primary pc and get the MULTIPLICITY response.

I can not telnet between the primary and secondary.  I have tried this using the port 30564.  I do have only allow connections from this subnet checked.  They do see each other, because the primary will show the laptop name and the vpn network ip for the secondary.  Local firewall shows that it is open for the port 30564  (I can't confirm once it leaves my PC and local router that it gets blocked via the vpn server, but I suspect it is blocking 30564.  I've tried port 80 for both and it still hasn't work, I'm no longer sure if it's port related.

I have reinstalled and updated a couple of times, since the issue has began.  Nothing has helped.

I do not know if I have a solution to resolve this.  I'm sure my company will not change their VPN system, I'm a small fish in a very large pond.  I've tried changing port addresses, but this hasn't helped.  I've got 2 network cards in both my Primary and Secondary PC, but that hasn't helped either.   I haven't tried firewire yet, I'm not sure if that will help, since the 2nd network cards have not.

Any help would be appreciated,

Thanks.

 

multiplicity
3,904 views 2 replies
Reply #1 from Stardock Forums Top
If you have rights to SSH to your hp box you can set up a tunnel there using a ssh client on your secondary .

http://www.ssh.com/support/documentation/online/ssh/adminguide/32/Port_Forwarding.html

(just some googled diagram , you'll get the idea if you read it)

You can map a server port on the host your ssh client is connected to .. then have your primary connect to that mapped port on the ssh server 'what you call hp box' , the data will be transfered to a port and address on one of your secondary 's nic's.

(this all depends on how much rights you get while using ssh.)

another way is to simply add a nic .

If you have shell rights on the 'hp box' you can install openvpn on it and make your own little vpn within the company's vpn.. and have your primary and secondary connect through there ( not making it the default route)


But as far as i see , you have a network problem entirely unrelated to multiplicity.. if you were wanting to transfer files from your primary to your secondary through FTP you'd have the same issue..
, this being said , if you give me all the information you can about that "hp box" what's installed on it (OS) etc etc.. what level of access you have to it , how much you can ask the administrator at work..
i can give you all sorts of possible workarounds..
Reply #2 from WinCustomize Forums Top
Great Info, which lead me to a work around. Quick summary of my issue: Once VPN into work, it (our network) blocks 2 VPN systems from seeing each other. Our hp box from internal can see both systems that have VPN to the network. Solution: Have the system forward the information, using the ssh. One time setup: On my main PC, within multiplicity. I added a secondary pc called localhost 127.0.0.1 and port 30500 Each day: (1) I log both of my PC's into work via VPN. (2) I get the ip address of my laptop (given out by the work domain). (3) On my main PC, I load up putty (nice little terminal software for unix and other systems) (4) Within putty, Under SSH and tunnels tab I enter. source port 30500 destination (Ip address from step 2 above, and port 30564) (5) I then connect to the unix box, which then forwards everything to my laptop. Multiplicity basically thinks my laptop is at 127.0.0.1:30500 Works great. Thanks for the help.
Multiplicity - Control multiple PCs using one keyboard and mouse