VPN - Client LAN and company LAN on same address schema

My company uses the default 192.168.1.0 255.255.255.0 scheme for our internal
LAN.

We have a VPN setup that gives VPN users connecting an IP address between
192.168.1.20 - 192.168.1.25

Of course, most home users have the 192 network as their default as well, so
when they connect to our VPN and try to send packets for our server of
192.169.1.2, their router see's the destination IP and does not forward it
out to the VPN.

I know having the user change their network to something else, such as the
200 network will solve the problem, but I am hesitant on having users jump
into their routers. Is there anything I can do on my end aside from
completely changing the companies internal IP's scheme to allow VPN users to
connect?

If you don't want to change the company IP range, your option is to setup
peer to peer routing, but you need to do that one by one. this search result
may help.

Solution for peer to peer VPN using the same IPYou may setup a different IP
range or subnet for peer to peer VPN. For example, in your case, you can use
IP 172.16.5.1 for the VPN host and 172.16.5.2 for ...
www.chicagotech.net/casestudy/peervpn1.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Jim A." <(E-Mail Removed)> wrote in message
news469FFEC-6667-4255-89BC-(E-Mail Removed)...
> My company uses the default 192.168.1.0 255.255.255.0 scheme for our
> internal
> LAN.
>
> We have a VPN setup that gives VPN users connecting an IP address between
> 192.168.1.20 - 192.168.1.25
>
> Of course, most home users have the 192 network as their default as well,
> so
> when they connect to our VPN and try to send packets for our server of
> 192.169.1.2, their router see's the destination IP and does not forward it
> out to the VPN.
>
> I know having the user change their network to something else, such as the
> 200 network will solve the problem, but I am hesitant on having users jump
> into their routers. Is there anything I can do on my end aside from
> completely changing the companies internal IP's scheme to allow VPN users
> to
> connect?