Routing queston

[Flint]

I have a win2k server used for RRAS. I have used a demand dial to connect
the RRAS to a netopia R9100 (Netopia runs a PPTP connection to the RRAS).
On the RRAS server itself, I can ping the Netopia and any PC behind it (have
static route for the remote site going through the demand dial). However, I
can't get the workstations behind the RRAS server to ping the netopia at the
remote location or any clients.

Clients behind the RRAS have a default gateway of a router (not the RRAS
server). Entering static routs on the workstations to the ip address of the
RRAS server doesn't work, since the demand dial doesn't have a local ip
assigned, I can't enter a static route to it either. Any suggestions would
be appreciated.

Thanks.

 

[Bill Grant]

There are two problems here. You need to get the traffic to the RRAS
router, then the RRAS router needs to route it through the tunnel.

To get the route working on the RRAS server, associate the static route
with the demand-dial interface. Using the new static route wizard in RRAS,
fill in the destination and netmask fields, but leave the gateway box blank.
Select the dd interface from the dropdown list. Now the route will be tied
to the interface, and will become active when the interface connects.

To get the traffic to the RRAS router, add a static route to the default
router to "bounce" the traffic to the RRAS router's LAN IP.

Does the Netopia have a route to send traffic for your subnet through
the tunnel?
You need routes at both ends for LAN to LAN connectivity.

 

[Flint]

Thanks Bill. I should have mentioned I tried that and that's where I am
stuck. Example, Workstation ip 192.168.0.5; Router 192.168.0.100. Win2k
RRAS 192.168.0.101. Demand Dial to Test. Static Route on RRAS on Demand
Dial Test; 192.165.0.0, mask 255.255.255.0 (tried 255 as well). Netopia has
PPTP connection to RRAS. Netopia Lan IP 192.165.0.99. Static Route on
Netopia 192.168.0.0 mask 255.255.255.0 gateway 192.165.0.99. Based on this
setup, the RRAS server can ping the Netopia and any workstations behind it.
The Netopia can ping the RRAS and any workstation behind it. The
workstations behind the Netopia can ping any machines in the 192.165.0.0
range.

What I can't do is ping from any workstation in the 192.168.0.0 to
192.165.0.0 even after entering a static route to the local ip of the RRAS
server. Tracert does confirm the request from the workstation is going to
LAN ip of the RRAS but it stops there. Any help would be appreciated.

Thanks.

 

[Bill Grant]

That looks pretty right to me. All I can suggest is to do a route print
from both routers when the link is up. Then check that each router does
indeed have an active route to the "other" subnet using the tunnel endpoint
as the gateway. The route on the RRAS server should become active when the
demand-dial interface connects.

If those routes are there, the VPN link should work just like a normal
IP router between the subnets (but a bit slower!)

 

[Flint]

RRAS has static route to end point using the demand dial interface. Remote
location on Netopia Router, static route to remote site via lan ip address
of the router. I tried changing it to the lan ip address of the rras and
that didn't work. The only thing the workstations can ping behind the rras
is the ip address that gets assigned when the demand dial interface is
connected.

Thank you for your assistance.

 

[RickB]

Flint,

Did you ever find a fix for this? I have the identical issue.

RickB