How to Create a Demand Dial PPTP Interface

Last reviewed: December 23, 1997
Article ID: Q177335
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Routing and Remote Access Service Update for Windows NT Server version 4.0

SUMMARY

With a Microsoft Windows NT Server computer that is using the Microsoft Routing and Remote Access Service (RRAS) Update, you may want to create a Point-to-Point Tunneling Protocol (PPTP) interface that automatically connects to a PPTP server when a resource is requested. This article discusses the steps needed to create a demand dial PPTP interface.

MORE INFORMATION

To configure a demand dial PPTP connection, use the following steps:

NOTE: The following procedure assumes that you have successfully installed RRAS and PPTP.

  1. From Routing and RAS Admin, right-click LAN and Demand Dial Interfaces and then click Add Interface.

  2. Use the Demand Dial Wizard to create a Demand Dial interface for a Point-to-Point (PPP) connection using a modem or ISDN RAS device and appropriate phone number.

    NOTE: In a branch office that uses the Internet, the phone number would be the phone number of the local Internet Service Provider (ISP).

  3. Repeat steps 1 and 2, but use a Virtual Private Network (VPN) RAS device and the IP address of the PPTP server.

    NOTE: In a branch office that uses the Internet, the IP address would be the IP address of the PPTP server's Internet interface.

  4. From Routing and RAS Admin, expand the IP Routing folder, right-click Static Routes, and then click Add Static Route.

  5. Create a static host route to the PPTP server's PPP interface. An example is shown below where the IP address of the PPTP Server is 192.100.100.1:

          Destination : 192.100.100.1
          Network Mask: 255.255.255.255
    
          Gateway     : 1.1.1.1
          Metric      : 1
          Interface   : PPP Connection to the ISP
    
    

  6. Create a static route (or routes) for the IP network IDs of the corporate intranet that will be accessed through the PPTP tunnel. An example is shown below where the corporate intranet network ID is 10.0.0.0:

          Destination : 10.0.0.0
          Network Mask: 255.0.0.0
    
          Gateway     : 1.1.1.1
          Metric      : 1
          Interface   : PPTP Connection to the Corporate network
    
    
The PPTP tunnel is automatically bought up through the following process (using the example information above):

  1. Packets destined for the network ID 10.0.0.0 are forwarded using the corporate intranet static route to the "PPTP Connection to the Corporate network" interface object.

  2. The PPTP Connection to the Corporate network interface object must establish a PPTP tunnel with the PPTP Server at its configured IP address of 192.100.100.1.

  3. To establish a tunnel, a TCP connection must be established.

  4. TCP connection packets to the address of 192.100.100.1 are forwarded to the "PPP Connection to ISP" interface object using the host route for the corporate PPTP Server.

  5. The "PPP Connection to ISP" interface is connected.

  6. The PPTP tunnel is connected over the PPP connection.

  7. Packets sent to the corporate intranet are sent over the PPTP tunnel.
Keywords          : nthowto ntnetserv ntrouter NTSrv kbnetwork
Version           : WinNT:4.0
Platform          : winnt
Issue type        : kbhowto


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.