VPN 2 Offices with Same IP Range/Subnet

I have two offices setup with the same IP Range/Subnet: Office A (XYZ.Ohio) 192.168.1.0/24, and Office B (XYZ.com) 192.168.1.0/24 - both have Server 2003 DC running AD.  Office A has a SQL 2005 and SQL 2008 servers, and Office B is running an Exchange 2003 server.

I want to setup a VPN between Office A and B so I know I have to change the subnet on one, but since they are both using the most common range I'm thinking of changing both to an uncommon subnet since VPNing into either has caused issues for remotes.  

My questions: 1. how involved is it to change the IP addresses/subnet on an AD network, running exchange and SQL servers, both DCs running DHCP server.
2. - what would be an uncommon and suggested subnet/IP ranges to use so we dont' confilict when Remotes VPN in to either office or conflict between offices.
dhasAsked:
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.

 
MikeKaneCommented:
I'll throw in my 2 cents....  

For the vpn issue, there are methods to vpn together 2 LANs with overlapping subnets.    IF you use cisco gear, this is well documented and I can provide links to the HOW TOs for this.  

If you want to change subnets, I usually shy away from the common ones that most comsumer routers would use.   So I tend to use 192.169.50.x/24,  192.168.51.x/24, etc.     Alternatively, use a 10.1.1.x, 10.1.2.x, etc...      

Changing a whole subnet to a new Range can be a little tricky.   I'm sure you can find better documentation on the process, but basically:
1) identify the subnets to change
2) select new range
3) identify any static assigned IP, identify any IPs with reservations
4) Set the DHCP lease time very low, like 3 hours.  So clients will frequently try to obtain new leases.
5) That night, canvas the subnet, redo the statics to the new range,
6) Create/activate the new dhcp range, create the new reservations.   ou will have new DNS and WINS servers most likely
7) Change the server's IPs make sure that AD DNS is updating as well.  Check and double check DNS
Follow MS's processes on changing the DC to a new subnet , there are articles covering this, just google it.  


0

Experts Exchange Solution brought to you by ConnectWise

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
 
goldeneagle3333Commented:
If you are using DHCP it should not be that complex.  I would make a list of all the static IP's and plan everything out in detail.  It is more complex to setup a site-to-site VPN.  
0
 
CuteadderCommented:
1. Change the dhcp range, change all the static ip's on the servers

2. Use a 10.*.*.* ip range
0
 
dhasAuthor Commented:
Thanks all.  I'm planning on using the 10.1.X.X range.  

I'm having difficulty finding any technet articles on changing the DC to a new subnet... but I'll keep looking.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.