Route through PPP direct connection

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



My goal is to route from a Windows XP box through an embedded
controller connected to the Windows XP box via a direct serial link
that is required to assign the IP address to the embedded controller.

I have a direct serial interface between an XP box and an embedded
controller that communicates via PPP. The XP box MUST supply an IP
address to the embedded device. So I created a new connection under
"Network Tasks" within the Network Connections Dialog and set up all
the parameters including the
Incoming TCP/IP properties to specify the IP address range to assign
the device.

Everything connects great.
I can send packets to the 192.168.1.82 device (embedded controller)
through the XP box.

I need to be able to route packets from the XP box to different IP
addresses on the embedded controller so I wanted to add a route to the
route table to allow routing of packets to the embedded controller and
use the embedded controller as a gateway.

When I attempted to add a route to the route table the route was
refused because the netmask on the IP address assigned to the XP box
side of the ppp connection was 255.255.255.255.

Is there a way to change the netmask assigned to the XP box PPP
interface?
Is there a way to set the Gateway on the PPP interface?
Is there any other way to allow packets destined for 192.168.2.0 to be
routed out the PPP interface?

I believe this is assigned by RAS and I could find no means to change
it using netsh.

Here are some details of what I see on the XP box:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x1000003 ...00 d0 59 3d 6e db ...... Intel 8255x-based Integrated
Fast Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.81 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.82 255.255.255.255 192.168.1.81 192.168.1.81
1
255.255.255.255 255.255.255.255 192.168.1.81 1000003
1
===========================================================================
Persistent Routes:
None

C:\Scripts>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Cable Disconnected

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.81
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :


C:\Scripts>ROUTE ADD 192.168.2.0 MASK 255.255.255.0 192.168.1.82
The route addition failed: Either the interface index is wrong or the
gateway do
es not lie on the same network as the interface. Check the IP Address
Table for
the machine.



===========================================================================
Attempt to change the subnet mask using netsh:

First find the interface name:
===========================================================================
C:\Scripts>netsh
netsh>interface
interface>ip
interface ip>
interface ip>show interface

MIB-II Interface Information

Index: 16777218
User-friendly Name: Internal
GUID Name: Internal
Type: PPP
MTU: 0
Speed: 0
Physical Address:

===========================================================================
First use a command that we know the syntax is correct:
===========================================================================

interface ip>set address name="Internal" source=dhcp

Error obtaining configuration for interface Internal.
.



Relevant Pages

  • Re: Windows 2000 RAS Server and a Cisco Client Router
    ... You need to use the method which a router to router connection uses. ... This involves setting up a demand-dial interface on the server. ... dropdown list as the interface to link with the route. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Cannot get NAT to route in RRAS
    ... ADSL Link was set as the Public interface in NAT, ... The static route also adds in fine using the ADSL Link interface, ... separate DNS server handles client’s requests, ... > Internet connection. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Return route not added on demand dial router
    ... on the server on the receiving end of the calls. ... using route print yields a different story. ... We have checked the user and interface names. ... In fact the gateway doesn't exist until you make the connection. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Return route not added on demand dial router
    ... > The resolution turns out to be a bit odd. ... >> The only time I have seen this is if the connection does not bind to the ... >> demand dial interface on the answering router. ... that explains why the static route isn't added. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Return route not added on demand dial router
    ... The only time I have seen this is if the connection does not bind to the ... demand dial interface on the answering router. ... From the RRAS console, can ... > using route print yields a different story. ...
    (microsoft.public.win2000.ras_routing)