The first thing to work out is whether this is a routing problem or just
a name resolution problem. If a remote user can ping a machine in the other
branch by its IP address, the problem is name resolution. If it can't, you
have a routing problem.
Do the remote users get IP addresses in the 10.10 subnet? This sort of
setup (called on-subnet addressing) uses proxy arp on the LAN to give the
remotes access and is not recommended for a routed network
You may need to put the remotes in their own IP subnet (ie off-subnet
addressing)
and use normal IP routing techniques to route between the three subnets. The
branch router would need to send traffic for the remote subnet through the
VPN connection.
Monster wrote:
> I have a site to site VPN setup (firewall to firewall) between our
> headquarters in Santa Clara and our Branch office in Ottawa.
>
> I use Microsoft routing and Remote access to allow telecommuters and
> travelling users access to the Corporate HQ network (10.10.x.x).
> These PPTP users can access all resources on the 10.10.x.x network
> but cannot access any resources at the branch office (192.168.x.x).
>
> Users that are physically connected at either office can access
> resources between the two offices without any problems.
>
> This leads me to believe that the problem may be with my RRAS
> configuration, but unfortunately I am no expert with the RRAS setup
> and cannot for the life of me figure out how to allow the PPTP users
> access to the branch office network.
>
> Any help with this would be greatly appreciated.
>
> Thanks
> Monster
|
Similar Threads
Linear Mode
