Behavioural difference in RRAS (API) between 2000 & 2003 Server


L

Lucas Modrich

Hi,

I am looking for technical assistance with an issue I have recently
encountered with an application we have interfaced to the RRAS API on Windows
2000 Server (i.e. MprAdmin…).

Our application is responsible for dynamically creating and dialling modem
based connections via RRAS. On Windows 2000 server the application performs
well and has not had any issues. Once we move to Windows 2003 Server (we have
tried both the initial 2003 & 2003 R2 SP2) the behavior changes, and it
appears that the routing information associated with the connection is being
removed (dropped?) as soon as the connection is established.


I have created an application that queries the RRAS interfaces and extracts
various pieces of information from them. It shows that as soon as the
connection is established on 2003, the information stored in the
MIB_IPFORWARDROW structure retrieved via a call to MprInfoBlockFind for the
interface is cleared - this does not occur on 2000, an I assume this is what
is causing our connectivity problems.

I retrieve the information via calls to the following API functions:
- MprAdminInterfaceGetHandle
- MprAdminInterfaceGetInfo
- MprAdminInterfaceTransportGetInfo
- MprInfoBlockFind

On 2000 we get the following information returned (some data not included):
Pre-dialout:
MPR_INTERFACE_2 Data:
Name: RRAS Monitor Connection
Intf Type: Full Router
Device Name: USB SoftV92 Data Fax Modem with SmartCP
Status: DISCONNECTED
Unreachability Reasons:
Options: IP Header Compression, Remote Default Gateway, Software
Compression, Require Encrypted Password, Secure Local Files, Require SPAP,
Shared Phone Numbers, Require CHAP, Require MS CHAP, Require MS CHAP2,
Phone Number: 312
Last Error: 0
IP Addr: 0.0.0.0
Device Type: modem
Dial Mode: 1
Type: 1

MIB_IPFORWARDROW:
Forward Dest: 10.30.1.1
Forward Mask: 255.255.255.255
Forward Type: 0
Forward Proto: 10006
Forward Policy: 0
Forward NextHop: 0


On Win2000 this data remains unchanged (except the connection state), and
our application can communicate with client applications on the other end of
the connection without problems.

On 2003 we get the following information returned (some data not included):
Pre-dialout:
As per details shown above for 2000.

Post-dialout (after connection is established):
MPR_INTERFACE_2 Data:
Name: RRAS Monitor Connection
Intf Type: Full Router
Device Name: Standard 56000 bps Modem
Status: CONNECTED
Unreachability Reasons:
Options: IP Header Compression, Remote Default Gateway, Software
Compression, Require Encrypted Password, Secure Local Files, Require SPAP,
Require CHAP, Require MS CHAP, Require MS CHAP2,
Phone Number: 312
Last Error: 0
IP Addr: 0.0.0.0
Device Type: modem
Dial Mode: 1
Type: 1

MIB_IPFORWARDROW:
Forward Dest: 1.0.0.0
Forward Mask: 0.0.0.0
Forward Type: 0
Forward Proto: 0
Forward Policy: 0
Forward NextHop: 0

As you can see the data in the MIB_IPFORWARDROW structure is changed. I
suspect this is preventing our application from correctly routing data to the
client application, and hence no communications.

Can you provide any advise as to where I should begin to look for
information on this issue, or who I should be discussing this further with. I
appreciate an assistance given.

Many thanks

Lucas Modrich
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top