CP_E75.10_NGX_R65_UpgradeGuide

14 March 2011

Upgrading to Remote Access Clients

for Windows 32-bit/64-bit

On NGX R65 SmartCenter Server

E75.10

© 2011 Check Point Software Technologies Ltd.

All rights reserved. This product and related documentation are protected by copyright and distributed under licensing restricting their use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form or by any means without prior written authorization of Check Point. While every precaution has been taken in the preparation of this book, Check Point assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice.

RESTRICTED RIGHTS LEGEND:

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19.

TRADEMARKS:

Refer to the Copyright page (http://www.checkpoint.com/copyright.html) for a list of our trademarks.

Refer to the Third Party copyright notices (http://www.checkpoint.com/3rd_party_copyright.html) for a list of relevant copyrights and third-party licenses.

http://www.checkpoint.com/copyright.html

http://www.checkpoint.com/3rd_party_copyright.html

Important Information Latest Documentation

The latest version of this document is at: http://supportcontent.checkpoint.com/documentation_download?ID=11998

For additional technical information, visit the Check Point Support Center (http://supportcenter.checkpoint.com).

Revision History

Date Description

14 March 2011 Initial version

Feedback

Check Point is engaged in a continuous effort to improve its documentation.

Please help us by sending your comments (mailto:[email protected]?subject=Feedback on Upgrading to Remote Access Clients for Windows 32-bit/64-bit E75.10 ).

http://supportcontent.checkpoint.com/documentation_download?ID=11998

http://supportcenter.checkpoint.com/

mailto:[email protected]?subject=Feedback%20on%20Upgrading%20%20to%20Remote%20Access%20Clients%20for%20Windows%2032-bit/64-bit%20E75.10

mailto:[email protected]?subject=Feedback%20on%20Upgrading%20%20to%20Remote%20Access%20Clients%20for%20Windows%2032-bit/64-bit%20E75.10

Contents

Important Information .............................................................................................. 3 Introduction to Remote Access Clients .................................................................. 5

Overview of Remote Access Clients ...................................................................... 5 Endpoint Security VPN ...................................................................................... 5 Check Point Mobile for Windows ....................................................................... 5 SecuRemote client ............................................................................................ 6

Using Different Management Servers .................................................................... 6 Why You Should Upgrade to Remote Access Clients............................................ 6 Before Upgrading to Remote Access Clients ......................................................... 6

Management Server and Gateway Requirements ............................................ 7 New Remote Access Clients Features .............................................................. 7 SecureClient Features Supported in Remote Access Clients ........................... 9 SecureClient Features Not Yet Supported ...................................................... 10

Configuring Gateways to Support Remote Access Clients ................................ 12 Installing Hotfix on Gateways ............................................................................... 12 Configuring SmartDashboard for Endpoint Security VPN and Check Point Mobile for Windows ............................................................................................................... 13 Configuring SmartDashboard for SecuRemote client .......................................... 17 Supporting Endpoint Security VPN and SecureClient Simultaneously ................ 19 Troubleshooting Dual Support ............................................................................. 21

Installing and Configuring Remote Access Clients on Client Systems ............ 22 Installing Remote Access Clients on Client Systems ........................................... 22 Using the Packaging Tool .................................................................................... 23

Preparing the Client Installation Package ........................................................ 24 Client Icon ............................................................................................................ 25 Helping Users Create a Site ................................................................................. 26

Preparing the Gateway Fingerprint .................................................................. 26 Using the Site Wizard ...................................................................................... 27 Opening the Site Wizard Again ....................................................................... 28

Connecting to a Site ............................................................................................. 29 Pre-Configuring Proxy Settings ............................................................................ 29 Pre-Configuring Always Connect ......................................................................... 30

The Configuration File ............................................................................................ 31 Configuration File Overview ................................................................................. 31 Customized Settings ............................................................................................ 31 Centrally Managing the Configuration File ........................................................... 31 Parameters in the Configuration File .................................................................... 33 Migrating Secure Configuration Verification ......................................................... 34

Multiple Entry Point (MEP) ..................................................................................... 35 MEP or Roaming .................................................................................................. 35 Configuring Entry Point Choice ............................................................................ 36 Defining MEP Method .......................................................................................... 36 Implicit MEP ......................................................................................................... 36

Configuring Implicit First to Respond ............................................................... 37 Configuring Implicit Primary-Backup ............................................................... 37 Configuring Implicit Load Distribution .............................................................. 38

Manual MEP ......................................................................................................... 39 Making a Desktop Rule for MEP .......................................................................... 39 Configuring Geo-Cluster DNS Name Resolution ................................................. 40

Differences between SecureClient and Endpoint Security VPN CLI ................. 41

Chapter 1

Introduction to Remote Access Clients

In This Chapter

Overview of Remote Access Clients 5

Using Different Management Servers 6

Why You Should Upgrade to Remote Access Clients 6

Before Upgrading to Remote Access Clients 6

Overview of Remote Access Clients Remote Access Clients E75.10 are lightweight remote access clients for seamless, secure IPSec VPN connectivity to remote resources. They authenticate the parties and encrypt the data that passes between them.

Remote Access Clients E75.10 are intended to replace the current Check Point remote access clients: SecureClient NGX, Endpoint Connect NGX, and NGX SecuRemote client NGX.

The clients offered in this release are:

Endpoint Security VPN - Replaces SecureClient and Endpoint Connect.

Check Point Mobile for Windows - New Remote Access Client.

SecuRemote client - Replaces NGX SecuRemote client NGX.

Endpoint Security VPN Replaces SecureClient and Endpoint Connect.

Enterprise Grade Remote Access Client with Desktop firewall and compliance checks.

Secure Configuration Verification (SCV) is integrated with Windows Security Center to query the status of antivirus, Windows updates, and other system components.

Integrated desktop firewall, centrally managed from SmartCenter server.

In-place upgrade from Endpoint Security VPN R75.

Requires the IPSec VPN Software Blade on the gateway, and an Endpoint Container license and Endpoint VPN Software Blade on the SmartCenter server.

Check Point Mobile for Windows New Enterprise Grade Remote Access Client.

Secure Configuration Verification (SCV) is integrated with Windows Security Center to query the status of antivirus, Windows updates, and other system components.

In-place upgrade from Endpoint Connect.

Requires IPSec VPN and SSL VPN Software Blades on the Gateway.

Using Different Management Servers


SecuRemote client Replaces the NGX SecuRemote client.

Basic remote access functionality.

Unlimited number of connections for Security Gateways with the IPsec VPN blade.

Requires a IPSec VPN Software Blade on the Gateway.

It is a free client and does not require additional licenses.

Using Different Management Servers Environments with SecureClient or NGX SecuRemote client already deployed can be easily upgraded to Remote Access Clients. The SmartDashboard for different versions of management servers is different. Use the documentation for the SmartDashboard that you have.

This guide is for the NGX R65 SmartCenter server.

If you have the R70.40 SmartCenter server, see Upgrading to Remote Access Clients on R70.40 Security Management (http://supportcontent.checkpoint.com/documentation_download?ID=11997).

If you have the R71.30 or R75 SmartCenter server, see Upgrading to Remote Access Clients on R71.30 or R75 Security Management (http://supportcontent.checkpoint.com/documentation_download?ID=11996).

Why You Should Upgrade to Remote Access Clients

Check Point recommends that all customers upgrade from SecureClient or Endpoint Connect to Remote Access Clients as soon as possible, to have these enhancements.

Automatic and transparent upgrades, with no administrator privileges required

Supports 32-bit and 64-bit, Windows Vista and Windows 7

Uses less memory resources than SecureClient

Automatic disconnect/reconnect as clients move in and out of the network

Seamless connection experience while roaming

Supports most existing SecureClient features, including Office Mode, Desktop Firewall, Secure Configuration Verification (SCV), Secure Domain Logon (SDL), and Proxy Detection

Supports many additional new features

Does not require a SmartCenter server upgrade

Remote Access Clients can coexist with SecureClient and NGX SecuRemote client NGX on client systems during the upgrade period.

Note - Check Point will end its support for SecureClient in mid-2011.

Before Upgrading to Remote Access Clients

Before upgrading, consider these issues.





Management Server and Gateway Requirements Remote Access Clients requires a supported gateway version. These Check Point versions support these E75.10 Remote Access Clients:

Check Point Gateway Version Supported for Endpoint Security VPN

Version Supported for Check Point Mobile for Windows

Version Supported for SecuRemote client

Gateway NGX R65 HFA 70 + Endpoint Security VPN R75/Remote Access Clients E75.10 Hotfix

Not Supported HFA 70 + Endpoint Security VPN R75/Remote Access Clients E75.10 Hotfix

Gateway R70 R70.40 + Endpoint Security VPN R75/Remote Access Clients E75.10 Hotfix

Not Supported To be supported on R70.50* (no Hotfix)

Gateway R71 R71.30 To be supported on R71.40* (no Hotfix)

R71.30

Gateway R75 R75 R75 + Hotfix from sk60940

To be supported on R75.10* (no Hotfix)

To be supported on R75.10 (no Hotfix)

VSX R67 To be supported on R67.10*

Not Supported To be supported on R67.10*

UTM-1 Edge firmware 8.2.33 firmware 8.2.33 To be supported on firmware 8.3*

Important Notes:

* shows that the version was not yet released.

Get all Hotfixes from sk61286 (http://supportcontent.checkpoint.com/solutions?id=sk61286).

See the Release Notes of the specific Check Point version for the supported platforms.

Additional Notes -

Remote Access Clients support VPN gateway redundancy with Multiple Entry Point (MEP). You can install the Remote Access Clients package on multiple gateways and must install it on the server to enable Implicit MEP.

The server and gateway can be installed on open servers or appliances. On UTM-1 appliances, you cannot use the WebUI to install Remote Access Clients.

Remote Access Clients cannot be installed on the same device as Check Point Endpoint Security R73 or R80. If Zone Alarm is installed on a device, you can install Check Point Mobile for Windows and SecuRemote client but not Endpoint Security VPN.

New Remote Access Clients Features This table describes new features in Remote Access Clients and on which Remote Access Clients they are available.

http://supportcontent.checkpoint.com/solutions?id=sk61286



Feature Description Endpoint Security VPN

Check Point Mobile for Windows

Secu- Remote client

Hotspot Detection and Registration

Automatically detects hotspots that prevent

the client system from establishing a VPN

tunnel

Opens a mini-browser to allow the user to

register to the hotspot and connect to the

VPN gateway

Firewall support for hotspots

Automatic Connectivity Detection

Automatically detects whether the client is connected to the Internet or LAN

Automatic Certificate Renewal in CLI Mode

Supports automatic certificate renewal, including in CLI mode

Location Awareness

Automatically determines if client is inside or outside the enterprise network

Roaming Maintains VPN tunnel if client disconnects and reconnects using different network interfaces

Automatic and Transparent Upgrade Without Administrator Privileges

Updates the client system securely and without user intervention

Windows Vista / Windows 7 64 Bit Support

Supports the latest 32-bit and 64-bit Windows operating systems

Automatic Site Detection

During first time configuration, the client detects the VPN site automatically

Note: This requires DNS configuration and is only supported when configuring the client within the internal network.

Geo Clusters Connect client system to the closest VPN gateway based on location.

Machine Idleness Disconnect VPN tunnel if the machine becomes inactive (because of lock or sleep) for a specified duration.

Flush DNS Cache Remove previous DNS entries from the DNS cache when creating VPN tunnel

Dead Gateway Detection

Tests that the Security Gateway is active by sending tunnel test packets.

Automatic Connectivity Detection

Automatically detects whether the client is connected to the Internet or LAN. If the network connection is lost, the client seamlessly reconnects without user intervention.



SecureClient Features Supported in Remote Access Clients

This table describes features in Remote Access Clients that existed in SecureClient, and on which Remote Access Clients they are available.



R75 Secu- Remote client

Authentication Methods

Username/Password

Certificate - CAPI/P12

SecurID (passcode, softID, key fobs)

Challenge Response

SAA

Cached Credentials Cache credentials for user login

NAT-T and Visitor Mode

Let users connect from any location, such as a hotel, airport, or branch office

Multiple Entry Point (MEP)

Provides gateway High Availability and Load Sharing and lets the Remote Access Clients connect to the VPN from multiple gateways.

Pre-Configured Client Packaging

Predefined client installation package with configurations for easy provisioning

Office Mode Internal IP address for remote access VPN users

Extended DHCP Parameters

When using Office Mode from a DHCP server, the gateway sends data that it got from the client to the DHCP server in the correct format - Hostname, FQDN, Vendor Class, and User Class.

Compliance Policy - Secure Configuration Verification (SCV)

Verifies client system policy compliance before allowing remote access to internal network

Proxy Detection Detect proxy settings in client system web browsers for seamless connectivity

Hub Mode Send all traffic from the client system through the VPN gateway

Localization Supported languages:

Chinese (simplified)

English

French

German

Hebrew

Italian

Japanese

Russian

Spanish





R75 Secu- Remote client

Certificate Enrollment and Renewal

Automatic enrollment and renewal of certificates issued by Check Point Internal CA server

CLI and API Support Manage client with third party software

Tunnel Idleness Detection

Disconnect VPN if there is no traffic for a specified duration

Dialup Support dialup connections

Smart Card Removal Detection

Detects when the Smart Card is removed and closes the active VPN tunnel.

Re-authentication After specified duration, user is asked for re-authentication

Keep-alive Send keep-alive messages from client to the VPN gateway to maintain the VPN tunnel

Check Gateway Certificate in CRL

Validate VPN gateway certificate in the CRL list

Desktop Firewall Personal firewall integrated into the client, managed with the SmartDashboard desktop policy. Logs are shown in SmartView Tracker.

Configuration File Corruption Recovery

Recover corrupted configuration files

Secure Domain Logon (SDL)

Establish VPN tunnel prior to user login

End-user Configuration Lock

Prevent users from changing the client configuration

Update Dynamic DNS with the Office Mode IP

Assign an internal IP address for remote access VPN users in the Dynamic DNS

SmartView Monitor Monitor VPN tunnel and user statistics with SmartView Monitor

Post Connect Script Execute manual scripts before and after VPN tunnel is established

Secure Authentication API (SAA)

Integrate with third party authentication providers.

SecureClient Features Not Yet Supported These features of SecureClient are not supported by Remote Access Clients. Many of these features are expected to be supported in the next release.



Feature Description

Single Sign-on (SSO) One set of credentials to log in to both VPN and Windows operating system

Entrust Entelligence Support Entrust Entelligence package providing multiple security layers, strong authentication, digital signatures, and encryption

Diagnostic Tools Tools for viewing logs and alerts

VPN Connectivity to VPN-1 VSX Terminate VPN tunnel at Check Point VSX gateways

DNS Splitting Support multiple DNS servers

"No Office Mode" Connect Mode Connect to the VPN gateway without requiring Office Mode

Pre-shared secret Authentication method that uses a pre-shared secret

Link Selection Multiple interface support with redundancy

Secondary Connect (Including Fast Failover)

Connect to multiple VPN gateways simultaneously and establish VPN tunnels to all resources located behind each VPN gateway

DHCP Automatic Lease Renewal Automatically renew IP addresses obtained from DHCP servers

Chapter 2

Configuring Gateways to Support Remote Access Clients

In This Chapter

Installing Hotfix on Gateways 12

Configuring SmartDashboard for Endpoint Security VPN and Check Point Mobile for Windows 13

Configuring SmartDashboard for SecuRemote client 17

Supporting Endpoint Security VPN and SecureClient Simultaneously 19

Troubleshooting Dual Support 21

Installing Hotfix on Gateways To upgrade from SecureClient or NGX SecuRemote client install the hotfix on production gateways or on a standalone, self-managed gateway. During the upgrade you can run Remote Access Clients on client systems along with SecureClient or NGX SecuRemote client.

If you already installed the Endpoint Security VPN R75 Hotfix on gateways, you do not have to install a new hotfix to use the new features of the Remote Access Clients.

To use the Implicit MEP feature, you must install the hotfix on the SmartCenter server. If you do not require this feature, the hotfix does not have to be installed on the server (only on the gateways).

Important: Before You Begin

If you choose to install the hotfix on a new dedicated gateway in the production environment, managed by the same management server as the rest of the Remote Access gateways, this gateway will also be added to the topology used by SecureClient clients. This causes them to connect to the new gateway. Thus, you must make sure the configuration is valid and that resources set by the encryption domain on this gateway are accessible.

Authentication with a pre-shared secret is not supported in this version. If you have users that are configured to use a pre-shared secret, you must configure them to use a different authentication scheme that is supported, for example username and password. For more about supported authentication methods see the Remote Access Clients E75.10 Administration Guide (http://supportcontent.checkpoint.com/documentation_download?ID=11992).

To install the hotfix on a Gateway:

1. Download the hotfix from the Check Point Support Center (http://supportcenter.checkpoint.com).

2. Copy the hotfix package to the gateway.

3. Run the hotfix:

On SecurePlatform:

[admin@gateway ~/hf]$ tar -zxvf hotfix_file.tgz

[admin@gateway ~/hf]$ ./fw1_HOTFIX_ENFI_HFA_EVE2_620631013_1

Do you want to proceed with installation of Check Point fw1 NGX R65

Support ENFI_HFA_EVE2 for Check Point VPN-1 Power/UTM NGX R65 on


http://supportcenter.checkpoint.com/

Configuring SmartDashboard for Endpoint Security VPN and Check Point Mobile for Windows


this computer?

If you choose to proceed, installation will perform CPSTOP.

(y-yes, else no):y

On Windows, double-click the installation file and follow the instructions.

4. If WebUI is enabled on the gateway, it must listen on a port other than 443. Otherwise, Endpoint Security VPN will not be able to connect.

5. Reboot the Gateway.


You manage Remote Access Clients through the SmartDashboard. This task explains how to set up the SmartDashboard to access configurations required for Endpoint Security VPN and Check Point Mobile for Windows. Before you begin, make sure you have a network for Office Mode allocation.

To configure SmartDashboard for Endpoint Security VPN or Check Point Mobile for Windows:

1. Set the Gateway to be a policy server:

a) In the Network Objects Tree, right click the Gateway and select Edit.



The Check Point Gateway - General Properties window opens.

b) In Check Point Products, select SecureClient Policy Server.

c) Open Authentication.



d) In Policy Server, select an existing user group, or create a new user group, to be assigned to the policy.

2. Configure Visitor Mode:

a) Open Remote Access.

b) In Visitor Mode configuration, select Support Visitor Mode.

3. Configure Office Mode:

Note - Office Mode is not available for SecuRemote client.



a) Open Remote Access > Office Mode.

b) In Office Mode Method, select Manual (using IP pool).

If you have a gateway cluster, allocate IP addresses for each cluster member. Do this in Cluster Member Properties > VPN tab > select Offer Manual Office Mode and then select IP Addresses.

c) In Allocate IP addresses from network, select the network for Office Mode allocation.

4. Click OK.

5. Make sure that the Gateway is in the Remote Access community:

a) Select Manage > VPN Communities.

The VPN Communities window opens.

b) Double-click RemoteAccess.

The Remote Access Community Properties window opens.

Configuring SmartDashboard for SecuRemote client


c) Open Participating Gateways.

d) If the Gateway is not already in the list of participating gateways: click Add, select the Gateway from

the list of gateways, and click OK.

e) Click OK.

f) Click Close.

6. For Endpoint Security VPN only, make sure that the desktop policy is configured correctly (Desktop tab).

7. Install the policy (Policy menu > Install).


You manage SecuRemote client through the SmartDashboard. This task explains how to set up the SmartDashboard to access SecuRemote client configurations.

Note - If you already configured SmartDashboard for Endpoint Security VPN and Check Point Mobile for Windows, these procedures are not necessary.

To configure SmartDashboard for Endpoint Security VPN:

1. On the gateway, configure Visitor Mode, if it is not already configured:



a) In the left navigation tree, select Remote Access.

The Remote Access window opens.

b) In Visitor Mode configuration, select Support Visitor Mode.

2. Office mode is not supported in SecuRemote client. On the Remote Access > Office Mode page, you can select Do not offer Office Mode. If you select a different option, it is ignored for SecuRemote client.

3. Make sure that the Gateway is in the Remote Access community:

a) Select Manage > VPN Communities.

The VPN Communities window opens.

b) Double-click RemoteAccess.

The Remote Access Community Properties window opens.

Supporting Endpoint Security VPN and SecureClient Simultaneously


In the left navigation tree, select Participating Gateways.

c) If the Gateway is not already in the list of participating gateways: click Add, select the Gateway from

the list of gateways, and click OK.

d) Click OK.

e) Click Close.

4. Install the policy.


To run Remote Access Clients along with SecureClient or NGX SecuRemote client on client systems, you must configure the server and the gateways that will manage these remote access clients.

Before you start the configuration, make sure that the encryption domains of all of the gateways are the same. Also make sure that all gateways give connectivity to the same resources.

To configure the gateways in SmartDashboard for management of Remote Access Clients and NGX clients:

1. For Check Point Mobile for Windows and SecuRemote client start with step 2.

For Endpoint Security VPN only, on the Desktop tab, add this rule to make sure that the Endpoint Security VPN firewall does not block SecureClient. Allow outbound connections on:



UDP 18231

UDP 18233

UDP 2746 for UDP Encapsulation

UDP 500 for IKE

TCP 500 for IKE over TCP

TCP 264 for topology download

UDP 259 for MEP configuration

UDP 18234 for performing tunnel test when the client is inside the network

UDP 4500 for IKE and IPSEC (NAT-T)

TCP 18264 for ICA certificate registration

TCP 443 for Visitor Mode

TCP 80

2. Open Policy menu > Global Properties.

The Global Properties window opens.

3. Open Remote Access > VPN - Advanced.

4. Select Sent in clear.

5. Click OK.

6. Select Policy > Install.

Troubleshooting Dual Support


Troubleshooting Dual Support If SecureClient blocks Remote Access Clients traffic:

1. Make sure that you selected Remote Access > VPN - Advanced > Sent in clear.

2. Choose how you want to solve this issue.

If users manage their own clients: they can delete the SecureClient site.

Note - It is not enough to disable the site. It must be deleted.

To solve this issue for all clients, change the Desktop rule base. In the Outbound Rules, add these rules above the rule that blocks the connection:

a) Allow traffic to the Endpoint Security VPN Gateway.

Desktop = All Users

Destination = Endpoint Security VPN Gateway

Service = http, https, IKE_NAT_TRAVERSAL

Action = Accept

b) Allow users to access the encryption domain.

Desktop = All Users

Destination = The encryption domain. In the example this is the FTP server.

Service = The protocol necessary to reach the encryption domain. In the example this is FTP.

Action = Accept

c) Install the policy.

To uninstall NGX Clients:

If you install Remote Access Clients after SecureClient or NGX SecuRemote client, and you want to uninstall the NGX client, you cannot do it from Add/Remove Programs. You must open the Uninstall SecureClient or NGX SecuRemote client program from Start > Programs.

To remotely uninstall SecureClient with a script, run: UninstallSecureClient.exe from the SecureClient installation directory.

Chapter 3

Installing and Configuring Remote Access Clients on Client Systems

In This Chapter

Installing Remote Access Clients on Client Systems 22

Using the Packaging Tool 23

Client Icon 25

Helping Users Create a Site 26

Connecting to a Site 29

Pre-Configuring Proxy Settings 29

Pre-Configuring Always Connect 30

Installing Remote Access Clients on Client Systems

The Remote Access Clients installation package is a self-installing executable that you can download from the Check Point Download Center.

If you uninstall a client to install or upgrade Remote Access Clients, you must restart the client when prompted.

If you set up an upgrade from the gateway (see Upgrading Clients from the Gateway in the Remote Access Clients Administration Guide (http://supportcontent.checkpoint.com/documentation_download?ID=11992)):

If users had Endpoint Security VPN R75, it keeps the existing settings.

If users had Endpoint Connect R73, it automatically upgrades to Check Point Mobile for Windows.


Using the Packaging Tool


When you use the packaging tool to give users an MSI for a manual upgrade, you can select which VPN client is in the package.

If you do not select a VPN client as part of the MSI:

If users already had Endpoint Security VPN R75, it keeps the existing settings.

If users do not already have Endpoint Security VPN R75, they can select a VPN client when they install the MSI.

If users had the Endpoint Connect R73 client, they can select a VPN client when they install the MSI.

Using the Packaging Tool You can create packages of the Remote Access Clients with pre-defined settings, such as which client to install, a VPN site and authentication methods. When you deploy the package to users, it is easier for them to connect quickly.

Remote Access Clients Administration mode lets you create pre-configured packages. You open one instance of the client, configure all settings, and save the client MSI.

Decide if you want to pre-configure the client package, and with which features. Then deploy the MSI package.

Some examples of client deployment options are:

Give each user a link to the default MSI file. Make sure that users have the gateway IP address.

Give each user a pre-defined MSI. The user runs the MSI and can connect as soon as installation is done.

For all installation types, make sure users have whatever is needed for authentication. For example, if users authenticate with certificates, make sure they have the certificate file before connection. Make sure they know that they must not delete this file.

You can distribute MSI files to users in different ways:

You can send an MSI file with GPO updates.

You can email a URL link to the client installation file on the gateway.

Using the Packaging Tool


If any of the required features are disabled on the client in Administration mode, change the configuration of the gateways.

Preparing the Client Installation Package To create a pre-configured package:

1. Download the E75.10 Remote Access Client Package MSI

2. Use the MSI to install a client on your computer.

3. Open the client in Administration mode:

32-bit systems - C:\Program Files\CheckPoint\Endpoint Connect\AdminMode.bat

64-bit systems - C:\Program Files(x86)\CheckPoint\Endpoint Connect\AdminMode.bat

4. Right-click the client icon and select VPN Options.

The Options window opens, with the Administration tab.

5. On the Sites tab, define the site you want clients to connect to.

6. Select the site and click Properties > Settings.

7. Select VPN options:

Always-Connect - Let the client connect automatically to the active site.

VPN tunneling - Make sure the client connects to the VPN for all outbound traffic. Enable Hub Mode for the gateway.

Authentication

8. Click OK.

9. Open the Advanced tab and select relevant settings.

Client Icon


10. Open the Administration tab.

a) Input MSI Package Path - Select the input MSI package file.

b) Replace user's configuration when upgrading - If you clear this, users keep their configuration after the upgrade. If you select this, the new configuration is merged with the old configuration. Users do not have to apply for new credentials to a site that they have been using.

a) Select a product that users will install: Endpoint Security VPN, Check Point Mobile for Windows, or SecuRemote client.

If you do not select a product, users can choose.

b) Click Generate to create the MSI package.

A window opens to select a location to save the generated package.

11. Distribute this package to Remote Access Clients users.

12. Users will double-click the MSI file and follow the on-screen instructions.

Note - On Windows Vista and Windows 7, there may be a prompt to allow access, depending on the UAC settings.

Client Icon The Client icon in the system tray notification area shows the status of Remote Access Clients.

Icon Status

Disconnected

Connecting

Connected

Encryption (encrypted data is being sent or received on the VPN)

Helping Users Create a Site


Icon Status

There is an issue that requires users to take action.

You can also hover your mouse on the icon to show the client status.

Helping Users Create a Site Each client must have at least one site defined. The site is the VPN gateway. If you did not pre-configure the client for a default site, make sure your users have:

The gateway fingerprint.

The gateway IP address or domain name.

The authentication method you want them to use.

Authentication materials (username, password, certificate file, RSA SecurID, or access to HelpDesk for challenge/response authentication).

Preparing the Gateway Fingerprint Before users define a site that leads to the gateway, prepare the fingerprint of the gateway. Users might get a warning that the client cannot identify the gateway and that they should verify the fingerprint.

Give the users the fingerprint to compare with their client installation and site definition.

To prepare the gateway fingerprint:

1. In SmartDashboard, click Manage menu > Servers and OPSEC Applications.

2. In the Servers and OPSEC Applications window, select the Certificate Authority and click Edit.

3. Open the Local Security Management Server or OPSEC PKI tab and click View.



4. In the Certificate Authority Certificate View window, copy the SHA-1 Fingerprint.

5. Send the fingerprint to users before they install the client.

Using the Site Wizard When the user first double-clicks the Remote Access Clients icon, a message opens:

No site is configured. Would you like to configure a new site?

If the user clicks No, the message closes. The user cannot connect to a VPN until a site is defined.

If the user clicks Yes, the Site Wizard opens.

To configure the first site of a client:

1. The user clicks Next.

2. The user enters the IP address or name of the VPN gateway.



If a DNS server is configured and the client is within the internal network, the client detects the VPN site automatically.

The wizard shows the progress while the Client resolves the site name or address to the actual gateway. This step in the wizard notifies the user that: This may take several minutes, depending on the speed of your network

connection.

If users see the certificate warning, make sure they check the fingerprint of the gateway:

a) Compare the site fingerprint with the SIC fingerprint on the gateway.

b) Click Details to see additional warnings.

c) If site details are correct, click Trust and Continue. The fingerprint is stored in the Windows registry and the security warning is not opened again for the site, even if the client is upgraded.

The wizard displays the authentication method step.

3. Give your users the authentication materials they need.

4. The user selects the correct method and clicks Next.

If Certificate, the user selects PKCS#12 or CAPI (make sure the user knows which to select), and clicks Next.

If SecurID, the user selects the type, and clicks Next.

If Secure Authentication API (SAA), the user selects that and a new page opens to select the type of SAA and the DLL file. If a DLL file is already configured for the site, users do not have to select a file. Then click Next.

5. The user clicks Finish and a message appears: Would you like to connect?

If the user clicks Yes, the client connects to the gateway and a VPN tunnel is created.

Opening the Site Wizard Again The Site wizard opens automatically the first time a client is opened. You can also open it at any time.

To create a new site on the client at any time:


Connecting to a Site


The Options window opens.

2. On the Sites tab, click New.

The Site Wizard opens.

OR

3. Right-click the client icon and select Connect to.

4. In the Site drop-down, select New Site.

The Site Wizard opens.

Connecting to a Site You might have to help users connect to the VPN. The Remote Access Clients let users connect to sites - where the site is the VPN gateway.

To connect to a site:

1. Right-click the client icon and select Connect or Connect to.

A site connection window opens.

This window has authentication fields according to the selected authentication method.

If you selected Connect to, you can select the site to which you would like to connect.

2. Enter credentials, and click Connect.

For SAA authentication, click Connect and then enter credentials.

A connection progress window opens. Wait until the connection is made.

Pre-Configuring Proxy Settings

Note - Remote-location proxy-server settings are usually detected automatically.

If a user is at a remote site that has a proxy server, the Remote Access Clients must be configured to pass through the proxy server to reach the gateway.

If you know that this will be an issue, you can configure this option when you prepare the client MSI file. Otherwise, you can help your user configure the proxy server when the issue comes up.

To configure proxy settings on the client:

1. In the Options > Advanced tab, click Proxy Settings.

Pre-Configuring Always Connect


The Proxy Settings window opens.

2. Select an option.

No Proxy - Make a direct connection to the VPN.

Detect proxy from Internet Explorer settings - Take the proxy settings from Internet Explorer > Tools > Internet options > Connections > LAN Settings.

Manually define proxy - Enter the IP address and port number of the proxy. If necessary, enter a valid user name and password for the proxy.

3. Click OK.

Pre-Configuring Always Connect You can help users set the Always Connect option. This lets the client connect automatically to the active site. In a default package, this option is available for users to change.

To configure Always Connect in the client:


The Options window opens.

2. On the Sites tab, select the VPN gateway, and click Properties.

The Properties window for the site opens.

3. Open the Settings tab.

4. Click Enable Always-Connect.

5. Click OK.

Chapter 4

The Configuration File

In This Chapter

Configuration File Overview 31

Customized Settings 31

Centrally Managing the Configuration File 31

Parameters in the Configuration File 33

Migrating Secure Configuration Verification 34

Configuration File Overview The gateways save configuration parameters in the $FWDIR/conf/trac_client_1.ttm configuration file.

After you edit and save the file, install the policy.

Note - When editing the configuration file, do not use a DOS editor, such as Microsoft Word, which adds formatting codes to the file.

Customized Settings If you customized the trac_client_1.ttm in a previous installation, you can restore your settings to the new $FWDIR/conf/trac_client_1.ttm file. Do not do this procedure if you did not change this file from its default settings - the new defaults, in the new file, are recommended for this installation.

You must not overwrite the new trac_client_1.ttm with the old one. The new file has added parameters that are necessary for Remote Access Clients operations.

To bring over customized settings:

1. See the difference in parameter values between the customized file and the new trac_client_1.ttm file.

Important - When copying settings from the backup TTM file, make sure not to copy the connect_timeout parameter.

If you do, the clients cannot connect.

2. For parameters that are common to the two files, you can copy the value from the customized file, to the new trac_client_1.ttm.

Important - Beware that you do not copy parameters or values that you did not manually change. The new file has changed, added, and deleted parameters that are necessary.

3. Save the file.


Centrally Managing the Configuration File If the configuration file on each gateway is identical, you can manage one copy of the configuration file on the SmartCenter server. This file is copied to the Gateways when you install the policy.

Centrally Managing the Configuration File


Important - You must use the newest configuration file installed on the gateway for Remote Access Clients. This is important, because if you do not install Remote Access Clients on the SmartCenter server, the server will have an outdated configuration file that does not support new features.

To centrally manage the configuration file:

1. On the gateway, save a backup of $FWDIR/conf/trac_client_1.ttm.

2. From the gateway, copy trac_client_1.ttm to the server.

3. Open $FWDIR/conf/fwrl.conf and find the % SEGMENT FILTERLOAD section.

4. Within this section, add this line:

NAME = conf/trac_client_1.ttm;DST = conf/trac_client_1.ttm;

This copies the file to the Endpoint Security VPN gateways whenever you run Install Policy.

5. Save the file and install the policy.

When clients download the new policy from the gateway, configuration changes are applied.

Parameters in the Configuration File


Parameters in the Configuration File This table shows some of the parameters of the TTM file. The default value is the recommended value.

Parameter Description Default

allow_disable_firewall Enable/disable menu option for user to disable desktop firewall.

Applied only if enable_firewall is true or client_decide.

false

certificate_key_length

certificate_strong_protection

certificate_provider

internal_ca_site

internal_ca_dn

Certificate enrollment settings. 1024

true

"Microsoft Enhanced Cryptographic Provider v1.0"

none

none

default_authentication_method Default authentication method. none

disconnect_on_smartcard_removal Enable/disable client disconnection when Smart Card with current certificate is removed.

false

do_proxy_replacement Enable/disable proxy replacement. true

enable_capi Enable/disable CAPI authentication. true

enable_firewall Enable/disable desktop firewall true, false, or client_decide.

true

enable_gw_resolving Enable/disable DNS resolution on each connection.

Used for MEP.

true

flush_dns_cache Enable/disable flushing the DNS cache while connecting.

false

hotspot_detection_enabled Enable/disable automatic hotspot detection. true

automatic_mep_topology Enable/disable the implicit (automatic) MEP method.

False - manual MEP method.

true

ips_of_gws_in_mep Gateway IP addresses for clients to connect to. Applied only if automatic_mep_topology is false.

Addresses are separated by "&#", and the list is terminated by a final "&#":

NNN.NNN.NNN.NNN&#MMM.MMM.MMM.MMM&#

none

Migrating Secure Configuration Verification


Parameter Description Default

mep_mode MEP mode, priority of Gateways defined in ips_of_gws_in_mep. Applied only if automatic_mep_topology is false. Valid values:

dns_based

first_to_respond

primary_backup

load_sharing

dns_based

predefined_sites_only Enable/disable user ability to create or modify sites.

false

send_client_logs Email addresses to which debug logs are sent. none

suspend_tunnel_while_locked Enable/disable traffic suspension if the machine becomes inactive (due to lock or sleep) for a specified duration.

false

tunnel_idleness_ignore_icmp Enable/disable monitor of ICMP packets to see if a tunnel is active.

true

tunnel_idleness_ignored_tcp_ports TCP ports that are not monitored to determine if a tunnel is active.

none

tunnel_idleness_ignored_udp_ports UDP ports that are not monitored to determine if a tunnel is active.

53&#137&#138&#

tunnel_idleness_timeout Time, in minutes, after which a client will close an inactive tunnel.

Zero (0) - the feature is disabled. The VPN tunnel will never close due to inactivity.

0

Note - sk42850 (http://supportcontent.checkpoint.com/solutions?id=sk42850) explains the complete file contents and syntax.

Migrating Secure Configuration Verification SecureClient uses SCV compliance checks, as do Endpoint Security VPN and Check Point Mobile for Windows. These features of SecureClient compliance are ignored by the Endpoint Security VPN client and Check Point Mobile for Windows:

user_policy_scv - This SCV check tests if SecureClient is logged in to a Policy Server. Endpoint Security VPN and Check Point Mobile for Windows do not log in to policy server, so this check is not necessary.

sc_ver_scv - This SCV check tests for the version of SecureClient. Currently, there is no SCV check for the version of Endpoint Security VPN or Check Point Mobile for Windows.

ckp_scv - This SCV check is not supported for Endpoint Security VPN or Check Point Mobile for Windows.

http://supportcontent.checkpoint.com/solutions?id=sk42850

Appendix A

Multiple Entry Point (MEP) Multiple Entry Point (MEP) gives high availability and load sharing to VPN connections. A Gateway is one point of entry to the internal network. If the Gateway becomes unavailable, the internal network is also unavailable. A Check Point MEP environment has two or more Gateways for the same VPN domain to give remote users uninterrupted access. Remote Access Clients automatically detect and use MEP topology.

MEP topology gives High Availability and load sharing with these characteristics:

There is no physical restriction on the location of MEP Gateways. They can be geographically separated and not directly connected.

In Manual MEP Gateways can be managed by different management servers. For Implicit MEP, Gateways must have the same management server.

There is no state synchronization in MEP. If a Gateway fails, the current connection falls and one of the auxiliary Gateways picks up the next connection.

Remote clients, not the gateways, find the Gateway to use.

To enable Implicit MEP, you must install the Hotfix on the SmartCenter server and on each Gateway. For Manual MEP this is not necessary.

In This Appendix

MEP or Roaming 35

Configuring Entry Point Choice 36

Defining MEP Method 36

Implicit MEP 36

Manual MEP 39

Making a Desktop Rule for MEP 39

Configuring Geo-Cluster DNS Name Resolution 40

MEP or Roaming For MEP to work with Endpoint Security VPN, you must disable or limit the Roaming feature. If a gateway connection fails, Roaming maintains the connection to the current gateway, while MEP finds a new gateway to connect to. If these two features were enabled at the same time, they would conflict with each other.

To limit roaming (and enable MEP):

1. Open SmartDashboard > Global Properties.

2. Open Remote Access > Endpoint Connect.

3. Set Disconnect when connectivity to network is lost to Yes.

4. Click OK.

5. Open GuiDBedit.

6. Find endpoint_vpn_implicit_disconnect_timeout and set it to 1.

7. Click Save.


Configuring Entry Point Choice


Configuring Entry Point Choice Configure how the client will choose a gateway from the multiple list of entry points.

First to Respond - The first Gateway to reply is chosen and the VPN tunnel is between that gateway and the client. The client asks for a response for each connection.

Recommendation: If you have multiple gateways that are geographically distant. For example, an organization has three gateways: London, Sundsvall, and Paris. Usually, the London Gateway responds first to clients in England and is their entry point to the internal network. If the London gateway goes down, these users access the network through the Paris or Sundsvall gateway that responds first.

Primary-Backup - One or multiple auxiliary Gateways give high availability for a primary Gateway. Remote Access Clients are configured to connect with the primary Gateway, but switch to a Backup Gateway if the Primary goes down.

Recommendation: If you have multiple gateways, and one is stronger or connects faster. Set the stronger machine as the primary. Clients use the backup if the primary is unavailable.

Load Distribution - Remote Access Clients randomly select a Gateway.

Recommendation: If you have multiple gateways of equal performance. The traffic of Remote Access Clients is shared between the gateways. Each client creates a tunnel with a random, available gateway.

Geo-Cluster DNS ame Resolution - You can enable Geo-Clustering instead of MEP, however we recommend MEP as it is easier to manage and give better performance. Geo-Cluster resolves Gateway DNS names based on location.

Defining MEP Method MEP configuration can be implicit or manual.

Implicit - MEP methods and gateway identities are taken from the topology and configuration of gateways that are in fully overlapping encryption domains or that have Primary-Backup gateways.

Manual - You can edit the list of MEP Gateways in the Remote Access Clients TTM file.

Whichever you choose, you must set the Remote Access Clients configuration file to identify the configuration.

To define MEP topology:

1. Open the $FWDIR/conf/trac_client_1.ttm configuration file.

2. Make sure that enable_gw_resolving is true.

3. Set the value of automatic_mep_topology

true - implicit configuration

false - manual configuration

4. Save the file.


Implicit MEP With Implicit MEP, the configurations of the gateways are used to make the VPN connections. Gateways are configured differently for each MEP method.

Before you begin, make sure that $FWDIR/conf/trac_client_1.ttm has:

enable_gw_resolving (true)

automatic_mep_topology (true)

Implicit MEP


Configuring Implicit First to Respond When more than one Gateway leads to the same (overlapping) VPN domain, they are in a MEP configuration. The first Gateway to respond is chosen. To configure first to respond, define that part of the network that is shared by all the Gateways into a single group and assign that group as the VPN domain.

To configure First to Respond MEP:


2. Open Remote Access > VPN Basic.

3. Make sure that Load Distribution is not selected.

4. Click OK.

5. For each gateway, open the properties window > Topology.

6. In the VPN Domain section, click Manually Defined and select the same VPN Domain for all Gateways.

7. Click OK.


Configuring Implicit Primary-Backup Configure the VPN Domain that includes the Primary Gateway and another domain that includes only the backup gateways. Configure each gateway as either the Primary gateway or a backup gateway.

To configure the primary gateway:

1. Open Global Properties window > VPN > Advanced, select Enable Backup Gateway.

2. In the network objects tree, Groups section, create a group of Gateways to act as backup Gateways.

3. Open the VPN properties of the Primary Gateway:

NGX R65 and R70: gateway properties > VPN

R71 and higher: gateway properties >IPSec VPN

Implicit MEP


4. Select Use Backup Gateways, and select the group of backup Gateways.

This Gateway is the primary Gateway for this VPN domain.

5. For each backup Gateway, make a VPN domain that does not include IP addresses that are in the Primary VPN domain or the other backup domains.

If the backup gateway already has a VPN domain, you must make sure that its IP addresses do not overlap with the other VPN domains.

a) Create a group of IP addresses not in the other domains, or a group that consists of only the backup gateway.

b) On the Properties window of the backup network object > Topology > VPN Domain section, select Manually defined.

c) Select the group.

6. Click OK.


Configuring Implicit Load Distribution To configure implicit MEP for random gateway selection:


2. Open Remote Access > VPN Basic.

3. Select Enable load distribution for Multiple Entry Point configurations.

4. Click OK.

5. For each gateway, open the properties window > Topology.

6. In the VPN Domain section, click Manually Defined and select the same VPN Domain for all Gateways.

7. Click OK.


Manual MEP


Manual MEP For implicit MEP (the method used by SecureClient), the gateways have to belong to the same VPN domain for MEP to function. For Remote Access Clients, if they are configured with Manual MEP, the gateways do not have to belong to the same VPN domain. The gateways are configured in the TTM file.

To configure the Gateways for MEP:

1. On a Gateway, open $FWDIR/conf/trac_client_1.ttm.

2. Search for the enable_gw_resolving attribute:

:enable_gw_resolving (

:gateway (

:default (true)

)

)

3. Make sure the attribute is set to its default value: true.

4. Search for the automatic_mep_topology attribute, and make sure its value is false.

5. Manually add the mep_mode attribute:

:mep_mode (

:gateway (

:default (xxx)

)

)

Where xxx is a valid value:

first_to_respond

primary_backup

load_sharing

dns_based - Use this to configure Geo-Clusters ("Configuring Geo-Cluster DNS Name Resolution" on page 40).

6. Manually add the ips_of_gws_in_mep attribute:

:ips_of_gws_in_mep (

:gateway (

:default (192.168.53.220&#192.168.53.133&#)

)

)

These are the IP addresses the client should try.

IP addresses are separated by an ampersand and hash symbol (&#)

The last IP address in the list has a final &#.

7. Save the file.


Making a Desktop Rule for MEP To use MEP, traffic to multiple sites in the encryption domain must be allowed. But the Desktop Policy sets the main site as the default Destination for outbound traffic. You must make sure that your policy allows traffic to the gateways in the encryption domain.

To add the MEP Rule:

1. In SmartDashboard, open the Desktop tab.

2. In Outbound rules, add a new rule:

Destination - a Group network object that contains all gateways in the encryption domain.

Service - the Visitor Mode service (default is 443), the NAT-T port (default is 4500 UDP), and HTTP.

Action - Allow.

3. Install the Policy.

Configuring Geo-Cluster DNS Name Resolution



You can enable Geo-Clustering instead of MEP, however we recommend MEP as it is easier to manage and give better performance. Geo-Cluster resolves Gateway DNS names based on location.

To enable Geo-Cluster DNS Name Resolution:

1. On the Gateway, open $FWDIR/conf/trac_client_1.ttm.

2. Change the :default attribute, located in the :enable_gw_resolving attribute, to true.

:enable_gw_resolving (

:Security Gateway (

:map (

:false (false)

:true (true)

:client_decide (client_decide)

)

:default (true)

)

)

3. Manually add the mep_mode attribute and set it to dns_based.

4. Make sure that the automatic_mep_topology is false.

5. Save the file.


To disable Geo-Cluster DNS Name Resolution (and enabling DNS IP address cache):

1. On the Gateway, open $FWDIR/conf/trac_client_1.ttm.

2. Do one of these:

Set the automatic_mep_topology to true

Set the mep_mode attribute to one of the options that is not "dns_based." See Manual MEP (on page 39).

Disable the MEP entirely by setting the enable_gw_resolving attribute to false.

3. Save the file.


Appendix B

Differences between SecureClient and Endpoint Security VPN CLI

This table shows common tasks and how to perform them with SecureClient or Remote Access Clients E75.10 command line. N/A indicates that the task cannot be performed with the CLI.

Task SecureClient Remote Access Clients E75.10

Asynchronous Connect connectwait <profilename> N/A

Change P12 Certificate Password

N/A change_p12_pwd -f <filename> [ -o <oldpassword> -n <newpassword> ]

Connect to Site connect [-p] <profilename> connect -s <sitename> [-u <username> -p <password> | -d <dn> | -f <p12> | -pin <PIN> -sn <serial>]

Create / Add Site add <sitename> create -s <sitename> [-a <authentication method>]

Delete Site delete <sitename> delete -s <sitename>

Disconnect from Site disconnect disconnect

Display Connection Status status N/A

Enable / Disable Hotspot Registration

sethotspotreg <on | off> N/A

Enable / Disable Policy setpolicy [on | off] N/A

Enroll ICA CAPI Certificate icacertenroll <site IP/name> <registration key> <file path> <password>

enroll_capi -s <sitename> -r <registrationkey> [ -i <providerindex> -l <keylength> -sp <strongkeyprotection> ]

Enroll ICA P12 Certificate N/A enroll_p12 -s <sitename> -f <filename> -p <password> -r <registrationkey> [ -l <keylength> ]

Get Site Name / IP getsite <profilename> info [-s <sitename>]

List Profiles listprofiles N/A

List Domain Names Stored in the CAPI

N/A list

Print Log Messages N/A log

Renew CAPI Certificate N/A renew_capi -s <sitename> -d <dn> [ -l <keylength> -sp <strongkeyprotection> ]


Differences between SecureClient and Endpoint Security VPN CLI

Task SecureClient Remote Access Clients E75.10

Renew P12 Certificate N/A renew_p12 -s <sitename> -f <filename> -p <password> [ -l <keylength>]

Restart VPN Services restartsc N/A

Set Certificate File / Password passcert <password> <certificate>

See Connect to Site

Set Username / Password userpass <username> <password>

See Connect to Site

Show Number of Profiles numprofiles N/A

Show VPN Client Version version ver

Start VPN Client Services startsc start

Stop VPN Client Services stopsc stop

Suppress UI Dialog Messages suppressdialogs [on | off] N/A

Unset User Credentials erasecreds N/A

Update Topology update <profilename> N/A

CP_E75.10_NGX_R65_UpgradeGuide

Documents

Transcript of CP_E75.10_NGX_R65_UpgradeGuide