XP - RAS - Routing

[esteevens]

Hello,

We are migrating 500 locations from NT4 workstation to XP Pro.
Currently these 500 locations each consist of 1 NT machine and a few
Unix machines networked together in a 140.x.y.0/24 network. The NT
machines also have an ISDN adapter and RAS for Dial out and Dial in.
The RAS server is configured with addresses 32.x.y.z. At the HQ site
we have a Cisco router which dials out whenever some machine in the HQ
network (128.1.0.0/16) needs access to one of the 500 locations. Each
location also kan dial in to the HQ.

If the HQ dials to one of the 500 locations, we have effectively
communication between the 128.1.0.0/16 and the 140.x.y.0/24 networks.
For this to work on NT4 we needed to add a permanent static route
128.1.0.0 mask 255.255.0.0 32.3.250.254. This will route all trafic to
128.1.0.0/16 from the LAN in one of the locations through the ISDN
adapter.

Now when we replace the NT machine by a XP machine, this route doesn't
seem to work anymore, or we cannot seem to add it with the route add
command. Is there a way to force all trafic to 128.1.0.0/16 through
the RAS connection?

 

[Robert L [MS-MVP]]

I would do the route in the Cisco router instead of each workstation, for example, route inside 140.x.y.0 255.255.255.0 128.1.0.1 1 (assuming 128.1.0.1 is Cisco router inside IP).


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hello,

We are migrating 500 locations from NT4 workstation to XP Pro.
Currently these 500 locations each consist of 1 NT machine and a few
Unix machines networked together in a 140.x.y.0/24 network. The NT
machines also have an ISDN adapter and RAS for Dial out and Dial in.
The RAS server is configured with addresses 32.x.y.z. At the HQ site
we have a Cisco router which dials out whenever some machine in the HQ
network (128.1.0.0/16) needs access to one of the 500 locations. Each
location also kan dial in to the HQ.

If the HQ dials to one of the 500 locations, we have effectively
communication between the 128.1.0.0/16 and the 140.x.y.0/24 networks.
For this to work on NT4 we needed to add a permanent static route
128.1.0.0 mask 255.255.0.0 32.3.250.254. This will route all trafic to
128.1.0.0/16 from the LAN in one of the locations through the ISDN
adapter.

Now when we replace the NT machine by a XP machine, this route doesn't
seem to work anymore, or we cannot seem to add it with the route add
command. Is there a way to force all trafic to 128.1.0.0/16 through
the RAS connection?

 

[esteevens]

I would do the route in the Cisco router instead of each workstation, for example, route inside 140.x.y.0 255.255.255.0 128.1.0.1 1 (assuming 128.1.0.1 is Cisco router inside IP).

I do not see how this would help the routing on the workstation.

A small scheme about the setup:

Unix machine LAN (140.8.0.201/24) ---- XP Pro LAN (140.8.0.15/24) ----
XP Pro ISDN (32.3.250.50) ---- Cisco Router ISDN (32.3.250.254) ----
Cisco Router LAN (128.1.1.254/16) ---- AS400 (128.1.1.2/16)

If we ping from the 128.1.1.2 to 140.8.0.201 the ping request arrives
at the 140.8.0.201 end. The reply is send out from 140.8.0.201 to
128.1.1.2. But... the unix machine sends its answer through it's LAN
adapter to his gateway (XP Pro LAN; 140.8.0.15) and then the XP Pro
machine does know what to do with the reply packet because the route to
the 128.1.0.0/16 network doesn't seem to work.

With windows NT4 this worked OK, with XP we cannot add the route to the
128.1.0.0/16 network (route add 128.1.0.0 mask 255.255.0.0 32.3.250.50
gives parameter error. Adding the IF number 0x10003 also fails, using
32.3.250.254 also fails...). It looks as if XP doesn't want us to add
this route anymore. NT did :-(