How to Use Connection Manager Administration Kit & routing table u

Discussion in 'Server Networking' started by Uche, May 5, 2006.

  1. Uche

    Uche Guest

    I really need Expert help.

    I have setup a VPN server:

    OS 2003 standard member of domain SP2
    2 nic card
    and 2 ip's

    If I manually connect to VPN server it works fine and do delete and adding
    of route everything is ok but if I use Connection Manager Administration Kit
    and which I have defined the route I will like to use and create the .exe
    file. Installing of the .exe file is ok but once it try to connect, it
    connects and disconnects with error
    “Connect action to update your routing table failed (80070057).†I looked
    at the VPN log, it say:

    ******************************************************************
    Operating System : Windows NT 5.1 Service Pack 2
    Dialer Version : 7.2.2600.2180
    Connection Name : test
    All Users/Single User : Single User
    Start Date/Time : 5/5/2006, 12:16:48
    ******************************************************************
    Module Name, Time, Log ID, Log Item Name, Other Info
    For Connection Type, 0=dial-up, 1=VPN, 2=VPN over dial-up
    ******************************************************************
    [cmdial32] 12:16:48 03 Pre-Init Event CallingProcess = C:\WINDOWS\Explorer.EXE
    [cmdial32] 12:17:04 04 Pre-Connect Event ConnectionType = 1
    [cmdial32] 12:17:04 06 Pre-Tunnel Event UserName = test Domain = vpn
    DUNSetting = test Tunnel DeviceName = TunnelAddress = 192.168.1.15
    [cmdial32] 12:17:05 07 Connect Event
    [cmdial32] 12:17:05 08 Custom Action Dll ActionType = Connect Actions
    Description = to update your routing table ActionPath = C:\Documents and
    Settings\tests\Application
    Data\Microsoft\Network\Connections\Cm\test\CMROUTE.DLL ReturnValue =
    0x80070057
    [cmdial32] 12:17:05 20 On-Error Event ErrorCode = -2147024809 ErrorSource =
    to update your routing table
    [cmdial32] 12:17:05 12 Disconnect Event CallingProcess =
    C:\WINDOWS\system32\cmdial32.dll
    [cmdial32] 12:25:15 04 Pre-Connect Event ConnectionType = 1
    [cmdial32] 12:25:15 06 Pre-Tunnel Event UserName = test Domain = VPN
    DUNSetting = test Tunnel DeviceName = TunnelAddress = 192.168.1.15
    [cmdial32] 12:25:15 07 Connect Event
    [cmdial32] 12:25:15 08 Custom Action Dll ActionType = Connect Actions
    Description = to update your routing table ActionPath = C:\Documents and
    Settings\test\Application
    Data\Microsoft\Network\Connections\Cm\test\CMROUTE.DLL ReturnValue =
    0x80070057
    [cmdial32] 12:25:15 20 On-Error Event ErrorCode = -2147024809 ErrorSource =
    to update your routing table
    [cmdial32] 12:25:15 12 Disconnect Event CallingProcess =
    C:\WINDOWS\system32\cmdial32.dll


    Please help
     
    Uche, May 5, 2006
    #1
    1. Advertisements

  2. Uche

    BS Guest

    Not sure whether this is helpful, but I just had to figure out how to use the
    bloody route update thing in CMAK, and the docs are poor, at best.

    A couple of points that are missed in the docs:

    1. The METRIC option is *not* optional. Failure to include it will result
    in failed connections due to an 0x8007000B error (not documented). A
    Microsoft poster on one forum incorrectly states that this is due to a
    corrupted CMROUTE.DLL.
    2. They should document the purpose of the REMOVE_GATEWAY command. See
    below...

    The basic approach that the routing table updates facility uses assumes that
    the default gateway is set to the remote gateway. This allows the "default"
    keywords to have some usefulness. But, using the remote gateway as the
    default is often not desirable. So, REMOVE_GATEWAY allows the remote gateway
    to be reset to its local default once the routes have been established on the
    connection.

    So, at least in my experience, the best option is to set things up with the
    TCP/IP Settings / "Make this connection the client's default gateway"
    (Gateway_On_Remote=1),
    and use REMOVE_GATEWAY once the routes are established. The following
    updates worked for me, for example:

    ADD 10.70.40.0 MASK 255.255.255.0 default METRIC default IF default
    ADD 10.70.42.0 MASK 255.255.255.0 default METRIC default IF default
    REMOVE_GATEWAY

    (Where my PPTP subnet is 10.70.41.0/24)

    -- Bill

     
    BS, Jun 5, 2006
    #2
    1. 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 (here). After that, you can post your question and our members will help you out.