VPN Subnets aren't able to communicate

  • Thread starter Thread starter James Lam
  • Start date Start date
J

James Lam

I have two remote offices both with their own subnet.
They are connected to the same Active Directory domain
through VPN to the head office. Both have connections to
head office but neither can connect with each other's
subnet through the VPN. Is that inherent in VPN? or else
what could be wrong?

Thanks for your help, could you let me know when you
respond via email.
 
In a typical hub and spoke VPN configuration, yes that is how it works.
The spokes only communicate with the hub. However, most VPN routers
can support VPN routing between spokes, make sure that the hub can
support that extra load on it in order to route all that traffic.

Mike.
 
Remember the remote offices have two paths. They have the Internet and they
have the path to the head office. To get to the remote offices they have to
have the routing setup to go via the head office. This has to be done
manually because the Default Gateway deals only with the Internet typically.

If all sites use for example 192.168.*.* for addrresses and the third octect
is used to determine subnets which then correspond to different sites, then
you use a static route on whatever the LAN routing device is that tells it
that anything destined for 192.168.*.* must be sent to the head office. Any
Firewalls or Proxys must also contain the entire 192.168.*.* range in their
LATs.

It is then up to the head office to know what to do with the traffic when it
hits them.
 
Back
Top