gosahd

Happy to say that the problem is solved. I think the problem got resolved by removing "Only allow connections from the subnet this computer is on" on Secondary Multiplicity client's Security settings. As soon as I removed that, the connection started working. Which also coincide with the observation that failure is at session or application layer and not at network layer. It is very basic setting and I must have picked up quickly at first glance, but somehow missed it.<b

Thanks Sean. Yes, those ports are open on both Draytek and ASUS routers for traffic from Primary to Secondary multiplicity clients. Should I also enable port forwarding from secondary to primary multiplicity client IPs ? Yes I am only configuring with IP as with name it complains. With IP it doesn't complain at the time of setting it up. It is when I click on GEAR symbol on Configure popup that is where I get that error. And the taskbar tray icon remains (disconnected).<

I have separated home and office devices via different subnets. Home subnet is 10.0.0.X (secondary PC) and office subnet is 10.1.0.X (primary PC). I can successfully ping and remote desktop from my secondary laptop to primary PC. But I am not able to connect from primary to secondary via multiplicity. Connectivity is like this below. When I traceroute, from primary PC I successfully hit till WiFi Router's WAN IP. I have configured port forwarding from primary PC IP to secondary lap