This article applies to inSync Cloud.
Overview
GeoFencing is an IP-based network filtering mechanism, in which only a specified IP address or a range of IP addresses is allowed to pass through. This IP address or the range of IP addresses is termed as scope. Connections outside the scope are blocked.
inSync Restore operation honors GeoFencing. This implies that you can perform a restore only when the request comes from the IP address present in the GeoFencing scope.
It is possible that the inSync user on Public Network, connected through VPN, may face issues when performing the restore even after connecting to the VPN.
The issue occurs mostly because the public IP address of the user's system is out of the GeoFencing scope. Most corporate VPNs use split tunneling due to which the public IP of the inSync user stays the same as provided by the internet service provider.
Verify IP address
You can verify the IP address in question by following steps.
Note the IP address of the inSync user's device using the following website:
https://www.whatismyip.com/Connect to the user's device through VPN but from outside the corporate network.
Again, note the IP address of the user's device using the following website :
https://www.whatismyip.com/Check whether both the IP addresses are same.
If the IP addresses are different, check whether the address obtained through VPN is included within the scope of the Public gateway IPs of GeoFencing on the inSync Management Console.
Allow restore over public IP
To allow restore over public IP, add the public IP within the scope of the public gateway using the following procedure to ensure the restore request from the public IP is allowed.
Log on to inSync Management Console..
On the menu bar, click Settingsmenu> Settings.
On the Settings page, open the Network tab.
Under Geofencing, click Edit.
On the Edit Settings window, enter the public IP address in the Public Gateway IPs box.
Click OK to save the IP.