|
It is possible to use Windows 2000's native client to establish a VPN connection
(a secure tunnel) between a remote Windows 2000 PC and Safepipe release
2.3 or newer. This guide describes the necessary procedures to be performed
on the Windows 2000 client PC:
- Installing a Safepipe certificate
- Creating an IP security policy
- Creating a security rule for the first tunnel endpoint (Safepipe)
- Creating a security rule for the second tunnel endpoint
(the Windows 2000 PC)
- Enabling a VPN connection to Safepipe
The relatively complex configuration procedure on the Windows
2000 PC is required in order to achieve a high level of security. However, you
only need to perform the procedures 1 - 4 once. The last procedure, 'Enabling
a VPN connection to Safepipe', must be performed every time you wish to (re)establish
a VPN connection to Safepipe.
With the purpose of minimizing the number of steps, the
procedures 2 - 4 are designed to be performed immediately after each other.
-
Safepipe must be configured
for the VPN connection with the Windows 2000 PC.
-
You must have received a certificate file and a certificate password from
the network administrator. Both were generated when Safepipe was configured
for the VPN connection.
-
You must know the IP address and subnet mask of the LAN subnet, to which
you will have access from the PC.
-
The PC must have a public (static) IP address and must be able to connect
to the Internet.
-
You must have installed the latest
Service Pack for Windows 2000 (Service Pack 2 or newer) on the PC.
-
You must be logged on as a user with administrator rights.
|
