VPN Client with local/remote subnet overlap

[JimInKS]

This is on an NSA2400 with enhanced OS.

Here is my problem.

I have a server at ip 192.168.1.18 that I would like to give remote access to via Sonicwalls Global VPN Client.

Of course, most home routers use 192.168.1.0/24 as default network. The net result is that the remote client can't see anything on our corporate network on that same subnet.

Sonicwall support says the the sonicwall vpn client can't route to a remote network when it overlaps with the local network. This does not make any sense to me as access to the local network is also lost when the vpn client is active. I had assumed that ALL traffic was being routed through the vpn connection. Any ideas on how to make this work?

I also have the option of setting up an SSL vpn, which I tried, but couldn't get to work. I just went with the standard vpn client because I knew it worked, and I only have 2 SSL vpn licenses.

 

[jebenson]

Are you using the virtual adapter on the VPN Client?



I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

Arrrr, mateys! Ye needs ta be preparin' yerselves fer Talk Like a Pirate Day!

 

[joepc]

Try using SSL-VPN and Netextender. I believe that allows you to get around the subnet issue.

In addition I know you can configure a site to site VPN even if the two local subnets are the same. You have to go into the NAT Policies and built a "virtual" 3rd subnet if you will to route. Sonicwall has a tech note on how to do this.

Anyhow you could try configuring the GVPNC use NAT policies and perhaps that will work just like a site to site VPN would.

Hope that can point you in the right direction.