> Source: [sk165494](https://support.checkpoint.com/results/sk/sk165494)

# sk165494 - Traditional Mode VPN connects to a wrong peer gateway

| Property | Value |
|----------|-------|
| Solution ID | sk165494 |
| Date Created | 2020-02-28 |
| Last Modified | 2020-08-31 |
| Technical Level | Advanced |
| OS | Gaia |

## Symptoms

- * Multiple Site-to-Site VPN tunnels are going down after creating a new gateway object. Running packet capture it can be seen that IKE negotiations or ESP packets are sent to a wrong peer gateway.
* Traditional mode VPN policy is configured, so there is no VPN community. VPN traffic is permitted by firewall policy rules.
* If IPSec VPN blade is disabled on the new created Check Point gateway object, VPN traffic starts to work correctly.

## Cause

Enable load distribution (random selection) was enabled. The option enables Implicit MEP, which caused the issue.

<br />

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content