Manuals / Allied Telesis / Computer Equipment / Network Router

Allied Telesis manual Configuring the VPN client, Add a new registry entry

Models: VPN

1 29

Download 29 pages 39.53 Kb

Page 8

Configuring the VPN client

Configuring the VPN client > Add a new registry entry

Configuring the VPN client

Configuring the Windows 2000 VPN client involves the following stages:

z"Add a new registry entry", on this page

z"Add the IP Security Policy Management snap-in" on page 9

z"Create an IP Security Policy" on page 11

z"Create an IP Security Rule" on page 13

z"Create an IP Filter" on page 16

z"Configure the connection" on page 23

Add a new registry entry

To ensure compatibility, you need to make a change to the registry. This Windows registry change allows the Windows client to bypass the default encryption scheme, and allows for user defined encryption parameters, or no encryption.

1.On your desktop, select Start > Run and enter the following command: regedit

Then click OK.

This opens the Registry Editor.

2.In the Registry Editor, browse to the following folder:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman\Parameters

3.Right-click on this folder and select New > DWORD Value. This creates a new entry.

4.Name the new entry “ProhibitIpSec”.

5.Double-click on the ProhibitIpSec entry. This opens a dialog box with the entry’s settings.

6.In the Value data field, enter 1. Click OK.

7.Restart Windows 2000 so that the changes take effect.

Page 8 AlliedWare™ OS How To Note: VPNs with Windows 2000 clients, without NAT-T

Image 8

Allied Telesis manual Configuring the VPN client, z Add a new registry entry, on this page

Contents

Consider the following typical scenario IntroductionAlliedWareTM OS Related How To Notes Which products and releases does it apply to?Security issue Example networkConfiguring the router Perform initial security configuration on the router1. Perform initial security configuration on the router, on this page 5. Set the router to use the configuration on pageThe configuration script Note Comments are indicated in the script below using the # symbol# add radius server=your-RADIUS-server-address secret=secret-key add ip int=vlan1 ip=office-private-LAN-address# Firewall enable fire create fire poli=main create conf=vpn.cfg set conf=vpn.cfg Set the router to use the configurationset conf=vpn.cfg Configuring the VPN client z Configure the connection on pageAdd a new registry entry z Add a new registry entry, on this pageAdd the IP Security Policy Management snap-in 2. Select Console Root Add/Remove Snap-InThis opens the Add Standalone Snap-In window 3. Click Add4. Click Add 5. Click Finish, then Close, then OK, to return to the Console windowConfiguring the VPN client Create an IP Security Policy Create an IP Security Policy2. Select Create IP Security Policy Configuring the VPN client Create an IP Security Policy 4. Click NextCreate an IP Security Rule 3. Click Next Page Create an IP Filter 4. Click Next This opens the IP Traffic Destination window. Select A specific IP Address from the Destination address drop-down box, as shown in the following figure. Enter the destination IP address of your Allied Telesyn router. This must be a valid Internet address 8. Click Next Configuring the VPN client Create an IP Filter7. Click Next 10. Select L2TP Tunnel Filter and click Next 9. Click Finish, then on the IP Filter List window, click Close11. Click Next 13. Click and then right-click on To Head Office, and select Assign. The policy is now assigned or enabled on your PC host, indicated by Yes in the Policy Assigned column, as shown in the following figure Configure the connection 2. Double-click the Network and Dial-Up Connection folderThe next window lets you assign an associated dialled call or select Do not dial the initial connection. Selecting Do not dial the initial connection is appropriate if you will have LAN access available before initiating the VPN call for example, if you have a cable modem 7. Click Next 10. Click Properties 11. Click OK Checking the connection from the Windows client Testing the tunnelTroubleshooting Closing the connection