@jeffwcollins:
No worries at all, remember there are a TON of actual network engineers that couldn't get this far either.
Ha! Thanks, I'm trying :)
In my opinion, for what its worth, there are ways to get around it but they get pretty complicated in the long term with sustainment in mind, meaning that there is no easy way to get this working with the configurations that are currently in place.
So, we'll be having a bunch of client appliances out at in the field (~20-40) so I'd really like to keep this as simple as possible. I'm keeping my fingers crossed that we don't run into more locations that happen to use the same network addressing.
Out of curiosity, Whats keeping you from changing the IP Scope of your site, instead of asking the remote office to change theirs?
The problematic network is our server VLAN :( So, we've got DCs, VMs, etc that are all hosted on that network, so changing that isn't really an option. We're actually blocking the client from accessing our server network as we want to limit outside access, but we want to be able to run scheduled tasks and do performance monitoring from that network to the clients in the field.
*To offer some transparency, one thing that could be considered is running a one-to-one nat across the VPN, but it could make sustainment a bit tedious in the long run. Just providing that as a possible fix for your problem.
Yeah, like I mentioned above, simplicity is ideal, especially when we're having to maintain a lot of these appliances. It looks like the easiest approach might be to see if the hosting site is willing to put us on a different network. We could care less what it is as long as it gives us access to the Internet.
thanks!
