Tr1al_us3r

Reply to Listening on wrong interface in ThinkDesk WinCustomize Forums

Hi Neil I was able to get the program working by setting the option option to restrict connections to the same subnet to disabled. In a private i.p. environment, this would probably work ok, as you'd be using the application just between two pc's on the same subnet. However, introduce a dialup connection on one, and you would have difficulties in having the program determine exactly which subnet to listen on (a dialup adapter is also a netwo

Listening on wrong interface in ThinkDesk Stardock Forums

Howdy! A friend got me to look at this app, pretty cool for a lightweight program, well done. I have two problem though; Each of my machines has two i.p. addresses - A private 10.x.x.x address in the same subnet, and a public 202.x.x.x in the same subnet. Locally, they talk to each other over the switch. The Primary machine is also occasionally on VPN, which gives that machine a third i.p. address. Problem 1: Multiplicity binds to 'an' i.p. address

Reply to Multiplicity Cannot Find IP of Machine After VPN Session in ThinkDesk Stardock Forums

I might suggest the following: 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