Information Technology Reference
In-Depth Information
￿ Send a Plain-Text Password If That Is the Only Way to Connect: Use this option only
if encrypted passwords cannot be sent, but beware that the passwords are highly
vulnerable to exposure.
￿ Use Scripting to Complete the Connection with the Remote Router: Select this
option if you need or want to run a script during the connection process.
9.
In the Static Routes for Remote Networks window, create a static route for the remote
network to which you want to connect your demand-dial interface. Enter the remote
network address and its subnet.
Note Make sure that you enter the address of the remote network and not of a particular host on the
network. For example, you may be connecting to a RRAS server at the remote address of 192.168.50.2 .
In this case, the remote network is specified as 192.168.50.0 , assuming a subnet of 255.255.255.0 .
10.
If you enabled the option to use scripting in step 8, you can identify in the Router Scripting
window the script that you want to run. You can select from a number of preconfigured
scripts supplied with the operating system, or you can create your own and use that
instead. All scripts, including the ones supplied with Windows, can be customized for
your environment. Click the Next button to proceed once you have selected your script.
11.
If you selected the option to add a user account in step 8, provide the password in the
Dial-In Credentials window. (The wizard will automatically create and name the account.)
Click the Next button to proceed.
12.
In the Dial-Out Credentials window, set the credentials that this interface will use when
connecting to a remote router. The credentials that you specify here must match
credentials configured on the remote router. Click the Next button to proceed.
13.
Click the Finish button to complete the wizard.
How It Works
You should create a demand-dial connection when you do not have a dedicated link to your
remote site but need to access resources on that site. The demand-dial connection is activated
only when data is sent to the remote network. Once activated, it remains connected until a
timeout period has elapsed, after which the connection drops until requested again.
Although your users could certainly create individual VPN connections to the remote site,
this is not practical when more than a few users require the connections. Administration is
more complex, since you must maintain VPN settings for each user that needs to connect.
Demand-dial connections are a better solution, since you only need to maintain the connection
on the two servers (routers), and all clients can then access resources on the remote network
with nearly the same effort as if they were on the local network. The amount of Help Desk
support that you will need to provide to individual users will be greatly reduced.
Search WWH ::




Custom Search