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

# sk166094 - Manual MEP 'first to respond' option not working as expected

| Property | Value |
|----------|-------|
| Solution ID | sk166094 |
| Date Created | 2020-04-09 |
| Last Modified | 2020-04-17 |
| Technical Level | Advanced |
| Products | Endpoint Security |
| Versions | Cloud, E89.X, E88.X |

## Symptoms

- * The client has MEP configured in 'first-to-respond' mode. The primary gateway where the client connects to is down. It is expected that the client will choose another gateway from the MEP list but connection process gets stuck.
* It also can be diagnosed by presence of specific line in `trac.log`:

  ```
  [proxy_wrapper] ProxyWrapper::handle_connectivity_analysis_request_queue: notify will do nothing if the state is INIT_STATE -> replace it with NO_PRX_STATE
  ```

## Cause

If connection to the primary gateway is not established, client decides to cancel all "probe" connection and chooses the first gateway on the MEP list.

## 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