I have a customer that have his server on IP 192.168.0.1.
He conntect the VPN and than connect to the server by doing RDP to 192.168.0.1
All going great from three locations.
The issue is that from one location the gateway (internet router) have the IP 192.168.0.1.
So he sucessefuly conntecto to the VPN, but can't do RDP to 192.168.0.1.
- Cloud managed firebox
- SSL VPN with Authpoint with AD Users
- Full tunnel
- Use Network DNS settings
Sign In to comment.
The issue here is that you have an overlapping network, so the local computer is not routing the traffic bound for 192.168.0.x to the VPN since it's the local network.
-I would suggest not using very common subnets like 192.168.0.x, 192.168.1.x, 192.168.100.x and 10.0.0.x as they're very often used on home routers.
See this doc for more information on reserved networks for private networks:
https://datatracker.ietf.org/doc/html/rfc1918 -- Address Allocation for Private Internets
Either the local or remote network will need to change their subnet to something else so it can be routable. I would suggest changing the firebox side, as you will keep running into this if you just change the other side.
WatchGuard Customer Support