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

# sk86401 - Connections with Hide NAT are dropped during policy installation due to NAT port allocation failure when CoreXL is enabled

| Property | Value |
|----------|-------|
| Solution ID | sk86401 |
| Date Created | 2012-10-24 |
| Last Modified | 2018-12-13 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * On Check Point appliances with over 12 CoreXL FW instances, connections from the Security Gateway with Hide NAT are dropped with no logging information.  

* Kernel debug ('`fw ctl zdebug -m fw + drop xlate`') shows:  
  `fw_first_packet_xlation: NAT rulematch failed (INBOUND) (ret=-1)`  
  `fw_log_drop: Packet ... dropped by fw_first_packet_xlation Reason: NAT rulematch failed`

## Cause

During policy installation, NAT port allocation fails due to the lack of available global ports for all CoreXL FW instances.

By default, the amount of global ports is 5 000 (range is between 60 000 and 65 000), and these ports are shared between all CoreXL FW instances.

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