Support Center > Search Results > SecureKnowledge Details
R70.50 Known Limitations
Solution

This article lists all of the known limitations of R70.50.

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:

For more information on R70.50 see the R70.50 Release Notes, R70.50 home page and R70.50 Resolved Issues.

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

 

ID Symptoms
  These Endpoint Security clients cannot connect to a SecurePlatform gateway when the WebUI is configured to use port 443:
  • SecureClient (Visitor mode only)
  • Endpoint Connect
  • Endpoint Security VPN client (R75)
  • Remote Access VPN clients (E75.10 and above)
You must configure the SecurePlatform WebUI to use a different port for management connections when using Endpoint Security clients.
00733220 Upgrade on a Solaris platform completes with an error. If you have Security Gateways 80 in your deployment with the IPS blade enabled, update the IPS database on the Management Server. Otherwise, you can safely ignore this error.
00849761,
00851798,
00851801		 When creating a new host node object, new option to select Management Blades can be seen in drop-down list.
01057490 Columns width under NAT policy on the GUI is not being saved.
01095224,
01096961,
01096962,
01096963		 Memory leak in the CPD daemon when using SmartProvisioning.
01096340 During policy installation the vpnd writes policy timestamp to cpras_topology_policy_id table, but the IKE process does not check it.
00528574 After establishing SIC or during policy verification, you might get an error message: "Incorrect reply from server. Command: private-db-dirty-check." The message can be ignored. Refer to sk44508.
01155362,
01157514,
01157515,
01157516,
01157518,
01158877,
01160701,
01162431,
01162675,
01173792,
01215306		 Cipher strength for Client Authentication is under 128-bit and there is no way to control the SSL version in use.
Important Note: Three new environment variables have to be added to disable the unwanted SSL versions - "ASSL_NO_TLS", "ASSL_NO_SSLV2", "ASSL_NO_SSLV3".
Refer to sk100584.
This solution is about products that are no longer supported and it will not be updated

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment