We can't see beyond our Dial-up VPN routers

[Steve]

Here is our situation. We have a domain and a workgroup
that we want to have a VPN connection between. We have
set up the demand dial VPN routers and they can see
eachother and browse eachother, but we can't get beyond
them. We know we are getting through the firewall because
they can see eachother's shares and ping. When we try to
connect to other servers on the same network, it fails.

We have tried adding static routes with route add, but
with no success. Also, when we go to the server in the
workgroup and connect to the other RRAS server as a client
(meaning, not a demand dial router), we can get to and
browse the other network perfectly. So the two servers
will funtion as a client/RRAS server relationship, but not
in a demand dial/demand dial relationship.

Our goal is to have the server in the workgroup join the
domain and become a domain controller for our remote site.

So again in short, when the servers connect as demand dial
routers, they can see and browse eachother, but we can't
get beyond them to the other machines.

 

[Bill Grant]

What you need to do is set it up as a router to router VPN connection.
This enables you to link the routing to the demand dial interfaces.

With a normal "dialup" type VPN, the routing is pretty simple and
doesn't allow routing to machines behind the caller. With a router to router
VPN, no routing is set up by default. But you can add static routes linked
to the demand dial interfaces. When the router connects, these routes
become active and allow you to route between the subnets behind the routers.
The connection works like a simple IP router between the two sites.

In addition to the info in Help, there is heaps of info at
www.microsoft.com/vpn . You can search on router to router or LAN to LAN .