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

# sk179710 - Error: new negotiations are not allowed! shows VPND debug on Check Point Security Gateway

| Property | Value |
|----------|-------|
| Solution ID | sk179710 |
| Date Created | 2022-08-19 |
| Last Modified | 2023-01-08 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.10 (EOS), R81 (EOS) |

## Symptoms

- * VPND debug on Check Point Security Gateway (per [sk14326](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=skI4326)) shows the following error.

  ```
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME] GetEntryIsakmpObjectsHash: received ipaddr: xx.xx.xxx.xx as key, found xxxxx: xxxxxx
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME] fwipsechost_from_ipxaddr: calling GetEntryXIsakmpObjectsHash for xx.xx.xxx.xx returned obj: xxxxxxx
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME] GetEntryCommunityHashX: called before hash initialization, could be because this entity is not in a community
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME] FindCommonCommunity: Did not find common community for vpn_test
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME][tunnel] handleNegotiationCapacity: Error: could not find community for vpn_test.
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME] fwisakmpd_process_incoming_data: Error: new negotiations are not allowed!
  [vpnd xxx xxxxxxxxxx]@HOSTNAME[DATE TIME][tunnel] KillNegotiation: Killing negotiation with no context (xxxxxxx)
  ```

* The Security Gateway does not initiate or accept the vpn negotiation when working in Traditional Mode.

## Cause

Traditional Mode is legacy has limitations.  

<br />

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 82
* [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 77

If you choose not to upgrade, 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).

**Note:**Traditional Mode policy is a legacy mode of defining IPSEC VPN that has limited features and it is not recommended any more.

<br />

---

# 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