I had a similar issue with R55 and Symantec firewall. The ID information
seems to be the hostname/ip address that both firewalls use as their
tunnel termination address.
please check:
in Check Point, the firewall object IP address is set to the internet IP
address, or better, the interface IP
Dear Ronny,
we found out that different routers need different "connectivity
enhancement" features set.
We are successful with Netgear routers with "force udp encapsulation"
for the configured site.
The "nothing else works" issue may, besides mtu problem, also be caused
if nat traversal dete
Dear Daniel,
you can apply predefined policies to secureclients this way
Login and fetch policy with your first client.
Find 3 files: \program files\checkpoint\securemote\policy\*.local
those files a somehow hashed and are bound to the specific client
installation.
Copy *.local files to the s
Dear Kalpesh,
it's me again...
I refuse to let you work with this configuration. The solution is to add
the office mode range to the UK encryption domain. As soon as US
Firewall knows about this it can establish an SA for this destination
network. Then UK firewall relays the traffic to the US
e that catches
10.10.2.0 and routes it to the US firewall. If not you will need a
routing entry in the backbone of US.
Martin Braun
SYSDAT GmbH
Kalpesh Patel wrote:
Hi
We have an issue, which I need your help on urgently please I need to
do more some testing with our Head office in the U.S
