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

# sk180175 - Cloning group peers are unable to join the cloning group

| Property | Value |
|----------|-------|
| Solution ID | sk180175 |
| Date Created | 2022-11-04 |
| Last Modified | 2022-11-07 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * If a cloning group was created by the affected environment, the peer member of the cloning group keeps trying unsuccessfully to connect:

  `Clish> show cloning-group status`  
  `Connecting to remote member...`
* 'xinetd' process does not start automatically.

* The output of "ps aux \| grep xinetd" does not show the xinetd process running.

* The 'service xinetd' commands do not work and do not produce any outputs

  `[Expert@admin]# service xinetd start`  
  `[Expert@admin]#`  
  `[Expert@admin]# service xinetd status`  
  `[Expert@admin]#`

## Cause

The configuration file '*/etc/sysconfig/network*' is missing essential lines.

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