Question
The SDP Client can't connect to remote resources, such as a network drive, and the connection times out. In addition, often the Client can't ping the remote resources.
Answer
This problem can be caused by overlapping subnets between the SDP user's home network and the site with the remote resources. Remote sites with an IP range of 192.168.0.0/24 or 192.168.1.0/24, can easily overlap with the IP range for home wireless routers (which often use this IP range as the default DHCP setting).
To troubleshoot this issue, compare the local subnet for the Client to the subnet for the remote resources.
- For Clients that support the LAN Blocking feature, you can enable LAN Blocking to resolve this issue.
- For other Client OSs, if the subnets overlap, then this is known limitation of the Cato Client. It doesn't support a common workaround that blocks access to the local network and sends all traffic through the VPN tunnel.
If possible, change the IP range for the remote corporate resources that overlap with the router IP range. Or you can change the DHCP settings for their wireless routers.
Comments
3 comments
Can this be updated now the LAN Blocking feature is available? I have had users at a Hotel WiFi where their Local IP overlaps with our internal WAN address space. Enabling LAN Blocking for the user resolved the issue.
Hello Nathan!
Thank you for highlighting this! I will contact our documentation team and ask them to update the article appropriately.
Kind Regards,
Dermot Doran (Cato Networks Community Manager)
Hello Nathan!
The article has been updated to reflect the fact that the "LAN Blocking" feature is now available. Thank you again for highlighting this for us.
Kind Regards,
Dermot Doran (Cato Networks Community Manager)
Please sign in to leave a comment.