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

# sk183072 - Fixing bi-directional connection issues in Quantum Security Gateways

| Property | Value |
|----------|-------|
| Solution ID | sk183072 |
| Date Created | 2025-01-29 |
| Last Modified | 2026-04-18 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * The Security Gateway drops the traffic. For example: @;416268071.163340;\[uspace\];\[tid_5\];\[SIM4\];resume_inbound_from_vm_reinject: dropping packet of for vsid=0 due to loop prevention (nloops=4, pkt_type VM Reinject, prev state Lookup, next state Lookup, in flags 0x4). conn: ;
* The connection for the specific UDP port used by Exchange servers for the sync is "Clear" while it must be "Encrypted".
* After the Security Gateway reboot, the connection is still "Clear".

## Cause

When a network connection is established simultaneously in both directions (server-to-client and client-to-server), the Security Gateway experiences connectivity issues because of incorrect packet dispatching, leading to dropped packets.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 25
* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 101

<br />

If you choose not to upgrade, **follow these instructions** :  
Enable the SIP handlers according to your network topology by following the instructions in [sk95369](https://support.checkpoint.com/results/sk/sk95369).
Alternatively, configure global parameters to specify port numbers for connections that may be established simultaneously from both directions.  

For that, run these commands in Expert mode:  

1. `fw ctl set int dispatch_port_1_tap <PORT_NUMBER>`
2. `fw ctl set int dispatch_port_tap_is_activated 1`

You can configure up to five ports with these parameters:  

* dispatch_port_1_tap
* dispatch_port_2_tap
* dispatch_port_3_tap
* dispatch_port_4_tap
* dispatch_port_5_tap

To disable this configuration, in Expert mode, run:  

`fw ctl set int dispatch_port_tap_is_activated 0`

<br />

Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/.contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

---

# 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