Information Technology Reference
In-Depth Information
11.
Select the Networking tab, and set the options in much the same way that you would
configure any network interface:
Click the Settings button to configure PPP options, including the use of LCP extensions,
software compression, and multilink negotiation. Click OK to accept the changes.
Add, remove, enable, or disable components that you want to use with this interface,
including protocol (TCP/IP, IPX, or network monitor driver), client (Client for Microsoft
Networks or Client Service for NetWare), or service (QoS Packet Scheduler, Network
Load Balancing, or Service Advertising Protocol). Additionally, select any of the
components and click the Properties button to specify additional details of each.
12.
Click the OK button to accept all changes.
How It Works
The term
demand-dial
routing can be somewhat misleading. Demand-dial connections are
typically initiated when a user on the local network requests resources from the remote network.
However, the connections can actually be configured as persistent ones that form when the
service is started and that never terminate (under normal operating conditions). This option
may be very convenient for organizations that do not need to worry about the expense of an
always-on connection and that want an always-ready connection.
As with any connection over the Internet, security should be a major concern. For this
reason, RRAS allows you to configure the method of authentication that you want to enable on
your connections. Always select the most secure method that can be implemented without
causing undue hardship to your end users. For example, if your remote users use Macintosh
clients, it does not make sense to use MS-CHAP v2 as the only allowed protocol, since this
protocol is not currently supported by the Macintosh operating system, and the users will not
be able to connect.
Make certain you have a solid knowledge of each authentication type and the ramifica-
tions of selecting one over another before you make the system available to end users.
See Also
Microsoft TechNet: “Understanding Demand-Dial Routing”
(
http://technet2.microsoft.com/WindowsServer/f/?en/Library/
48757b3c-9211-48b6-a057-7ec71406f44a1033.mspx
). This article discusses the basic
concepts and issues behind demand-dial routing.
Microsoft KB 278880: “The Demand-Dial Interface Does not Disconnect When Network
Address Translation Is Installed.” This article contains information regarding the DNS
proxy and its effect on demand-dial connections.
Microsoft TechNet: “Troubleshooting Demand-Dial Routing”
(
http://technet2.microsoft.com/WindowsServer/f/?en/Library/
0cb97fcf-ca9f-40fb-b543-5ed93696c8861033.mspx
).
Recipe 5-3 for basic information on configuring demand-dial interfaces.
