Local and VPN IP subnets are both 192.168.1.x

Our LAN uses 192.168.1.x IP addresses.  One of our vendors has just required us to connect to their VPN, then RDP to one of their computers to conduct business.  Their network also uses 192.168.1.x IP addresses.  Our network is small, so the effects have been minimal, but only by luck it would seem.  Sometimes we are forced to re-login to our own file server, and this is cumbersome and inconvenient.  How can we adjust settings on our end to minimize/eliminate IP address conflicts?  Our networking equipment is SOHO.  One perhaps obvious solution would to change our entire subnet internally, but that just doesn't seem like the best way to proceed.  Advice please?
K AAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joe FulginitiNetwork EngineerCommented:
What VPN client are you using to connect?
Christian KAZADiIT HELPDESKCommented:

The only professional way to do this is to do a network re-addressing. If by chance you have a DHCP server, this would minimize the time blow. it's a lot cleaner than anything else.

Christian K.
Rob WilliamsCommented:
Basic rules of routing state that subnets (network IDs) in any two network segments must be different in order for routing to take place.  If using a VPN client, as I assume you are if you are assigned certain options you may be able to access one remote device, but not multiple.  The only solution to work properly is to change your local addressing.  For this reason it is a good reason to never use common subnets like:
192.168.0.x, 192.168.1.x, 192.168.2.x, 192.168.111.x, 10.0.0.x, or 10.10.10.x

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Maximize Customer Retention with Superior Service

The IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more to help build customer satisfaction and retention.

SeanSystem EngineerCommented:
Usually you need the networks to be different. This is a big problem with VPN but it's pretty difficult to fully get around. Need to change a network to a different subnet.
K AAuthor Commented:
Thanks, Joe... It's a Fortinet client.

Thanks, Christian... our router does DHCP for us.  We'll probably use that to adjust our IP addresses.

Thanks, Rob and Sean also... At least there's a little comfort to me that I kind of knew what the (simple) solution would be...

I'm going to leave this question open for a little longer in case somebody has a new, genius idea,,,   arrrghh... I blame the vendor AND us for choosing such a popular IP subnet.
Rob WilliamsCommented:
Same subnets is probably the most common VPN question on EE.

Pete Long explains how you can use the same subnet at both ends with Cisco routers. It's quite a read and quite brilliant.
K AAuthor Commented:
Thanks, Rob... Nicely done... Don't think we can do that with a $100 Linksys router... :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.