Evaluate how the outbound Remote
Access Server for Internet Access is being configured.
For example, will your
client have a modern broadband or other permanent, high-speed Internet
access connection? Or will the Remote Access Server have to provide
dial-up Internet access?
If using the Remote Access
Server is being used for dial-up Internet access through Proxy Server, how
often during the day are end users connected for Web browsing or Winsock
applications (Outlook, Outlook Express, etc.)?
Note: If your
clients' end users are “typical”, they may be connected most of day to
the Internet through a Web browser or other Winsock applications. If so,
this basically means this modem and analog line will not be
available for other purposes. So plan the Remote Access Server
accordingly.
Look at inbound Remote Access
Server needs.
For example, how often
will end users be dialing into the Small Business Server? How many end
users will have dial-in capability to the Remote Access Server portion of
Small Business Server? How long does a typical dial-up session with the
Remote Access Server last? For even a small number of Remote Access
Server-capable end users dialing in from home or on the road will dictate
dedicating at least one modem to inbound Remote Access Server functions.
The goal of any
Remote Access Server rollout is usually to make end users’ “on the
road” experience, as similar as possible to their in the office
experience. Although bandwidth will dictate slower speed, the performance
still needs to be “acceptable.” So be sure to take this into account.
Look at whether direct-dial
Remote Access Server access is required.
Or whether some or all of
the end users can leverage PPTP to bypass the dial-up portion of the
Remote Access Server and create virtual private networking (VPN)
connections with the Small Business Server. When fully-configured on
clients, PPTP end users can run the same dial-up networking applications
setup, just with different phone book entries and Desktop shortcuts.
To use the PPTP-based
Remote Access Server, end users first dial into their local ISP. Then
using an additional DUN phone book entry and connection, a PPTP connection
is initiated through the Internet to the Small Business Server.
Note: If most end users will be connecting to the
Remote Access Server through PPTP, your client only needs one or perhaps
two direct-dial RAS setups with modems and analog lines. And the only
reason to have these is for backup and fault tolerance when either the
user’s or the full-time Internet access connection is down. PPTP
doesn’t actually require a full-time connection. However, most PPTP
implementations are based on servers with static IP address, registered
DNS domain names, and full-time Internet access connections.
For More Free Small Business Server Consulting Tips
Just click on the banner below and sign up for our
sponsor's free training audio recording.
|
