Multitech RF760 User's Guide Page 131

  • Download
  • Add to my manuals
  • Print
  • Page
    / 189
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 130
Chapter 7 – User Authentication Methods
Multi-Tech Systems, Inc. RouteFinderVPN RF760/660/600VPN User Guide (PN S000323D) 131
Authentication Setup
Choose one of the following setup methods.
Setting Up RADIUS Authentication
To set up RADIUS Authentication, first you need a RADIUS server on your network. The server can be anywhere on the
Internet, but keep in mind that passwords are transferred in clear text. Therefore, we strongly recommend putting the
RADIUS server somewhere near your RouteFinder and to use a switched Network hub to connect them.
Choosing the RADIUS server is up to you. Below is some generic setup information.
The RouteFinder will send a RADIUS authentication packet with three fields:
1. Username
2. Password in plain text (PAP)
3. The proxy type ("http" or "socks") in the NAS-Identifier field based on these values, your RADIUS server should
just decide to grant or deny access.
Setting Up A Microsoft IAS RADIUS Server
This section explains how to set up a Microsoft IAS (Internet Authentication Server). IAS is delivered with all Windows
2000 Server versions. However, it is often not installed by default. For NT4, IAS comes with the "NT4 Option Pack"
(available for "free"). The Windows 2000 IAS version has many more features than NT4 IAS; however, the NT4 version
is also sufficient for a typical RouteFinder authentication setup. Below are some generic IAS step-by-step instructions.
1. Check if the IAS service is installed. If not, install it.
2. Using NT/2000 User Manager, edit the user profiles of all Users who should use proxy services, and set the
"Dial-In Permission" flag. This is necessary since IAS uses the "master flag" to respond to requests positively.
3. Create a new user group for each proxy service you wish to provide to your users. For clarity, give the groups
descriptive names (for example, call the group "multitech _http_users").
4. Put the users in the newly created groups for using the respective proxy services.
5. Enter the IAS administration interface at
(Start->Programs->Administrative Tools->Internet Authentication Service), and add a new client using
these settings:
Friendly Name: routefinder
Protocol: RADIUS
Client Address: Use the address of the RouteFinder's interface pointing "towards" the RADIUS
server (this will be the "internal" interface for most people).
Client Vendor: RADIUS Standard
Uncheck the Client must always send signature attribute ... box.
Select a shared secret. You will need this later in RouteFinder configuration.
6. Go to the policy list. There is one pre-defined entry. Delete it. Add a new Policy for each proxy service you
wish to provide to your users. Choose the "Friendly Name" accordingly ("SOCKS access" for example).
7. On the next screen, add two conditions:
NAS-Identifier matches <string> (where <string> is the proxy identifier, currently "socks" or "http")
Windows-Groups matches <yourgroup> (where <yourgroup> is one of the newly created user groups).
Note: You can add groups from the local machine or from Domains in which the RADIUS server is a member.
User may have to specify the user name as <DOMAIN>\<USER> for authentication to succeed.
8. Choose Grant Remote Access Permission in the next screen.
9. Edit the profile on the next screen. Select the Authentication Tab. Check Unencrypted Authentication (PAP).
10. Click OK and Finish. Remember you need one policy for each proxy service.
11. Configure the RADIUS authentication method on the RouteFinder (you will need the IP of the IAS server and
the shared secret), and use the RADIUS authentication method in User Authentication > RADIUS & SAM
settings.
12. Check the System Log in the NT/2000 Event Viewer; that's where NT/2000 puts information about RADIUS
authentication requests.
Page view 130
1 2 ... 126 127 128 129 130 131 132 133 134 135 136 ... 188 189

Comments to this Manuals

No comments