Home Page | Skip to Navigation | Skip to Content | Skip to Search | Skip to Footer
 Support Center > Search Results > SecureKnowledge Details
Support Center
 Print    Email
Endpoint Security VPN for Mac E75 Known Limitations

Solution ID: sk69623
Product: Endpoint Security VPN
Version: E75
Date Created: 09-Apr-2012
Last Modified: 09-Feb-2014
Rate this document
[1=Worst,5=Best]
Solution

This article lists all of the known limitations of Endpoint Security VPN for Mac E75.

This is a live document that may be updated without special notice. We recommend registering to our weekly updates in order to stay up to date. To register go to UserCenter > My Profile > My Subscriptions.

Important notes:

  • To get a fix for an issue listed below contact Check Point Support with the issue ID.
  • To see if an issue has been fixed, search for the issue ID in Support Center.

For more information on Endpoint Security VPN for Mac E75, refer to:

Visit our discussion forums to ask questions and get answers from technical peers and Support experts.
Popular forums:

 

Issue ID Symptoms
00861912 MEP configuration is not properly supported when a restrictive outbound desktop firewall policy is enforced.
00864585 If a restrictive desktop firewall policy is enforced, FTP sometimes does not work properly.
00857475 In the Desktop Firewall policy, logs from rules that have"Alert" selected in the Track column are not uploaded to the gateway.
00885833

The Proxy Detection and Replacement feature has these limitations:

  • CIDR network names in the proxy bypass list are not supported (for example, 169.254/16).
  • Proxy authentication settings are not read from the system configuration. They are read from 'VPN options > Advanced tab > Proxy Settings'.
  • When proxy replacement is activated, users will not see changes in MAC OS X System Preferences UI.
00885275

After Endpoint Security VPN is installed and a client is connected to the gateway, automatic sync with Time Capsule and iPhone Wi-Fi sync might not work correctly.

This can happen because of a restrictive Desktop Policy.

To resolve this issue, allow these services in the "Inbound rules" of the Desktop Policy:

  • SSDP: UDP, port 1900.
  • mDns: UDP, port 5353.

00852752

The Extended DHCP Parameters feature is not supported in this release. This means that Automatic Office Mode Allocation Method (Using DHCP) configured for the Gateway might not work correctly for this client.

00872699

In the Desktop Policy Rule Base, a group or groups in the Desktop column cannot contain more than 123 elements. If more than 123 elements are included in the Desktop column in a rule, the client drops the gateway connection.

Workaround: Split the group into 2 or more groups and define 2 or more rules for the groups.


Give us Feedback
Rate this document
[1=Worst,5=Best]
Additional comments...(Max 2000 characters allowed)
Characters left: 2000