User`s guide

USER’S GUIDE
18 SFVRA Connection Manager
CLIENT PC REQUIREMENTS
• 33/66 MHz 486-class PC
•8 MB RAM
•2 MB free disk space
•Windows NT
3.51 with service pack 2 or higher, or Windows 95
®
• Network connection to SQL Server
• 32-bit ODBC drivers
• Keyboard, mouse, and color monitor
POLICIES FOR CONFIGURATION
When you are planning to provide a dial-in service for remote users, there are important policies
to define in order to configure it successfully.
• Device level security should be used for all remote users. This is generally PAP or CHAP for
PPP users and CPP for combinet users. Windows NT security may be used to authenticate the
remote user’s password. SFVRA-CONN allows CLID to be used individually or in combina-
tion with other types of security.
• If there is more than one CyberSWITCH with pooling enabled, you should carefully design the
use of hunt groups for the ISDN lines. If the hunt group spans the system, bandwidth should
be restricted from remote sites to a single B-channel. This restriction ensures that another con-
nection is not made from another Remote Access Switch to support the additional bandwidth.
In addition, each Remote Access Switch should be configured with the same system name, PAP
password, CHAP secret and IP WAN interfaces, so that the remote site is not aware of the Re-
mote Access Switch on which the connection was established.
• IP addresses for subnets and individual hosts should be assigned based on the following
criteria:
• Are the interfaces on the WAN numbered or unnumbered? Make sure that all remote users
support unnumbered before choosing it.
• Can RIP v.2 be used to advertise routes at the central sites? Many other venders’ routers do
not support this version. If RIP v.1 must be used, the same subnet mask is recommended
for all subnets.
• Are individual hosts going to be assigned addresses statically or will they be assigned
dynamically when they connect? Dynamic assignment is preferred because it preserves
addresses, but it can be used only for dial-in users.