This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Remote IP Subnet is same as LAN IP Subnet traffic won't route
Local Office LAN IP Subnet is 192.168.1.0
Remote Home LAN IP Subnet is 192.168.1.0
VPN Client connects but nothing routes. I beleive this is because both LANs are on the same subnet. Is there any way to configure the Remote Client Setup to allow this to work or do I have to put the Remote User's LAN on a different Subnet.
BTW: that is what I did to fix it on one client but I have many home users with Routers that default to use the 192.168.1.0 subnet.
Yes: Shame on me for leaving my office LAN on the default Subnet of 192.168.1.0.
The only solution here is to change the LAN IP Subnet to a different IP address range. It is either you change the IP address range of the Local Office LAN IP Subnet or Remote Home LAN IP Subnet
The only solution here is to change the LAN IP Subnet to a different IP address range. It is either you change the IP address range of the Local Office LAN IP Subnet or Remote Home LAN IP Subnet
