| All Categories |
Primers
VPN, Firewall, Security ... |
Guides
HowTo, Choosing a VPN ... |
Reference
Articles, FAQs, Whitepapers ... |
Standards
Architectures, Protocols ... |
Downloads
VPN, Firewall, Security ... |
Products & Services
Hardware, Software, Services |
| Organizations |
Business
Market Research, Law ... |
| Forums |
News
Archive, Events, Newsletters ... |
|
|
| |
| VPN labs is an open community for researching, testing, reviewing, and discussing Virtual Private Networks. Get trusted, unbiased advice on just about everything related to VPN. For more detail check: How to use this site. VPN Labs - VIRTUAL PRIVATE NETWORKS - Free VPN Software and Virtual Private Network News. |
|
|
|
|
atreus769
Member since:
2006-11-17 08:38:55 |  posted: 2006-11-17 08:45:29
routing
----------
We just setup a branch
office at work and have a
VPN from there to our
main office to do all of
their work. Most of our
stuff is done in a remote
location that everyone
connects to from the main
office. This is the
schema of the
network:
Main
Office LAN -
172.22.12.0
Remote
Location Router -
172.22.12.1
For
everyone at the main
office they have a route
add because the specific
app goes to 172.21.1.0 or
172.29.13.0 through the
remote router. Now the
branch office is VPN'ed
into us but the only way
I could get them to work
was to setup the local
network as 172.21.1.0 but
they can't get on to the
internal network. When I
set it up with the local
network as 172.22.12.0
they can get on the local
network but can't use the
remote location. We are
using router to router
vpn but i can't figure
out what to do? The
branch office network is
172.22.11.0. What I need
it to do is
this:
172.22.11.0
-> VPN ->
172.22.12.0
After
being on that network I
need them to be able to
access 172.21.1.0 through
172.22.12.1
I've
tried the route add but
it won't let me because
of the gateway. All
machines are running
Windows XP SP2 |
|
