- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- IKE failure - no response from peer
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IKE failure - no response from peer
Hi there,
I would like create IPsec from checkpoint to transit gateway, but I got following error msg 'IKE failure' and 'no response from peer'. (please see the screenshot)
I would really appreciate if someone can help me with this issue.
Thanks a lot.
Casey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There are multiple scenarios, some troubleshooting is required. Follow the SK guidance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From my perspective and my experience, best next step when facing this message is to consult logs of the peer gateway and perform debug on the peer as well.
In most cases i had there was a mismatch between Phase1 or Phase2 config of the participating gateways and when facing this message i usually find something useful on "the other side"
Cheers
Vincent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Casey,
how do you resolved this : IKE failure - no response from peer ?
I have similar issue. On my case , it not a routing issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I solved it by changing the VPN Tunnel Sharing from subnet pair to each pair for host in the Tunnel Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In my case it happened to me with a Cisco router, the problem was in an ACL on the remote peer, associated with the interface as INBOUND match condition, where the esp 500 udp port was being permit, but it blocked the nat-t 4500 udp and the VPN was armed with NAT-T
We made rules to accept that port but still nothing. Just leaving a rule on the Cisco router like "permit ip any any" everything work.
In your case I see reject...... with checkpoint.
