Windows 2000 RAS Server and a Cisco Client Router

[Mathias Gummert]

I set up a Win 2000 RAS server and use a Cisco router as dial-in
client.

So far so good. The connection comes up as it is supposed to and I can
ping the router from the Win2000 RAS server PC as well as the Win2000
box from the router.

The problem is that a PC in the Cisco´s network cannot ping the
Windows 2000 box and vice versa. (It can ping the Cisco).

There are (static) routes on the Cisco to both PCs (Win 2000 and own
network´s PC).

This is the PPP configuration of the Win2000 box during an existing
PPP connection to the Cisco:

The problem seems to be that there is no default gateway for the PPP
connection.

I could not find a way to add a default gateway for a RAS Server PPP
connection.

I tried to add a default route to the ppp interface manually (using
the route add command), but I could not do this for reasons I don´t
understand (e.g.:

or like this:
Schnittstellenindex >>ungültig oder das Gateway befindet sich nicht im
gleichen Netzwerk wie die >>Schnittstelle. Überprüfen Sie die
IP-Adresstabelle für diesen Rechner.
)

In Windows it´s possible to add a default gateway for an outgoing RAS
connection - but how about a Windows box acting as RAS server?

How can I add a default gateway for a RAS Server connection or just a
route to the remote PC?

Can anybody help?

Thank you in advance.

Mathias...

 

[Bill Grant]

You need to use the method which a router to router connection uses.
This involves setting up a demand-dial interface on the server.

Configure a demand dial interface, and add a static route (using the new
static route wizard in RRAS). You select the demand dial interface from the
dropdown list as the interface to link with the route. Set up an account
with dialup privileges with the same name as the demand dial interface.
Check that the option "allow a router to connect" (or whatever it says in
German!) is checked.

When you connect from the Cisco, use the name of the demand dial
interface as the username. The Cisco will then connect to the dd interface
instead of the default internal interface. The route back to the Cisco's
subnet will be added to the routing table through the link. (The default
option only sets up a host route back to the calling machine, since it is
designed for a simple client-server connection, not another router).

The advantage of this method is that you don't need to know what IP
address the connection uses. You just use the name of the demand dial
connection, and the system looks after it. And the route is automatically
added and removed when the remote router connects or disconnects. When not
in use, the static route is stored in the registry.