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 how you configure Safepipe for the
connection.
-
On Safepipe's management interface, click 'Tunnels' > 'Windows 2000
Tunnel'.
-
On the 'Options' tab, enter the network address and corresponding subnet
mask of at least one and no more than five subnets on your LAN, to which
the users of Windows 2000's native client may have access.
-
Click on the 'Generate' button to create a CA (Certificate Authority) certificate
on Safepipe that can verify the users of Windows 2000's native client. This
will take several minutes.

Afterwards, the 'CA date' field will display the present date.
-
On the 'Users' tab, click the 'Add Tunnel' button.
-
Click the <Not Configured> link
in the 'Name' column of the new tunnel.
-
Enter a name for the user of Windows 2000's native client. Enter a certificate
password to unlock the certificate file on the user's PC.
If you leave the 'Certificate Password' field empty,
a random password will be generated by Safepipe.
-
Click the 'Apply Changes' button.
-
Safepipe will now generate a certificate file for the user. Once the certificate
file is generated, the 'Certificate File' field changes from displaying
<Not Configured> to displaying
Download. Click on the 'Download' link
to save the certificate file for the remote user onto your hard disk or
a diskette.
-
Click on the 'Windows 2000 Tunnel' icon to return to the 'Users' tab, where
the new Windows 2000 tunnel should now be displayed with the name you entered
and the status <Not Connected>.
-
Enable the tunnel by clicking the 'Enable' button.
-
To proceed with the configuration of the remote Windows 2000 PC, follow
the guide How to configure Windows
2000 native client for a connection with Safepipe.