Ask the Community
Groups
In Classic Live Connect VPN connection is established but cannot connect to the remote network - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>SYMPTOMS</strong></p> <p>Live Connect > VPN function (KVPN) reports a successful connection, but there is no network connectivity to the remote network (pings do not respond).</p> <p><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fcommunity.kaseya.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-wikis-components-files%2F00-00-00-00-21%2FKKB001018.png"><img src="http://community.kaseya.com/resized-image.ashx/__size/550x0/__key/communityserver-wikis-components-files/00-00-00-00-21/KKB001018.png" alt="" class="embedImage-img importedEmbed-img"></img></a></p> <p> </p> <p><strong>CAUSE</strong></p> <p>The KVPN plug-in is unable to automatically add a route to the remote network on the Live Connect user's computer. This is a known limitation affecting all 64-bit versions of Windows.</p> <p> </p> <p><strong>SOLUTION</strong></p> <p>The problem will be addressed programmatically in a future version of Kaseya.</p> <p>Currently, the missing route must be added manually on the Live Connect user's computer. Here are the steps to achieve this: -</p> <p> </p> <p>1) establish VPN connection</p> <p>2) check the "assigned IP" of the VPN tunnel. In the above screenshot this is 192.168.212.2 but the sub-net address will depend on the local and remote network addresses. It will always end in .2 though.</p> <p>3) run the following command from Windows command shell (cmd.exe): -</p> <p>route add 172.16.29.0 mask 255.255.255.0 192.168.212.1</p> <p> (where 172.16.29.0/255.255.255.0 is the remote sub-net address and 192.168.212.1 is the <strong>agent</strong> side VPN tunnel address. This will be same sub-net as the "assigned IP" displayed in KVPN, but ending with .1 instead of .2).</p> <p> </p> <p>It should now be possible to ping IP addresses on the agent's network.</p> <p> </p> <p><strong>APPLIES TO</strong></p> <p>Kaseya VSA</p> </article> </main>