Client VPN to same subnet as source

You have to change the subnet on one end. That is the best way to solve this problem. Normally changing the subnet on one end is easy. I use 192.168.100 on my home office network and no client has this subnet.

I cannot change the subnet on either end unfortunately.

I have not ever seen a situation where you cannot change one end. So you are stuck.

There are some ways to get it working, but all are more sophisticated. And depending on the client VPN software you might not be able to use any. So:

1. Which VPN client are you using?
2. Which VPN gateway?
3. Is the remote IP (not the subnet) used in your client network?

E.g. if you only need to RDP into 192.168.0.123, and that address isn't used on your LAN, then it might work to set a specific route for only this IP.

@ie0 - You only allowed 6 minutes before you said "impossible". Have you asked the client end?  Normally change the subnet on the router and restart the modem, router and all computers.

The remote computer is a Macbook.
The VPN termination point is a Sonicwall TZ
The client software is the Sonicwall client (netextender)

The remote location is a time share, hence no access to the subnet.
I cannot re-subnet the office network just for this.

Thanks

If permanent timeshare, install your own router and use a different subnet on the extra router.  This will introduce NAT Traversal but you can work with that.

Wireless access in the condo only, no ethernet cable.

You may have to equip this user with a USB Internet card. I have one of these and I have used it when one client had the same subnet as another client. This works.

John, can you describe the usb internet card some more as I don't understand what it is.
thanks.

John,
This requires a cell phone signal.
My post probably was not clear enough, I need to use the internet service I am given in the condo, not pay for another one.
Thanks.

Then you have to convince one end or the other to change.

SonicWall NetExtender is restrictive. We've switched back to using published apps when accessing a client, because exactly that issue (being on the same network - it is 192.168.100.0 :D, that much about choosing a unique one ...).

It is feasible to write up a local batch file establishing the connection, then doing some necessary fixes like changing the routing table. But this needs special adjustment on your side, and detailled information about what NetExtender sets up on connection. And of course it is flaky, because of the changes, so getting connection failures might occur, requiring to try a few times before it works.

Qlemo,
What do you mean by using "published apps"  is this a sonicwall feature?