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

# sk180916 - Endpoint VPN for Windows fails to connect using machine certificate with the error "certificate is badly signed"

| Property | Value |
|----------|-------|
| Solution ID | sk180916 |
| Date Created | 2023-04-30 |
| Last Modified | 2023-05-07 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Windows |

## Symptoms

- * End users of Endpoint VPN Client for Windows cannot connect to resources behind the VPN Gateway.
* Endpoint VPN Client for Windows shows the error message "*certificate is badly signed*".
* The Check Point administrator deployed a new machine certificate with a new intermediate Certificate Authority (CA). The new machine certificate has the same name/subject name and is signed by the same root CA as an existing machine certificate.
* The certificate repository of the Windows endpoint computer contains duplicates of the old intermediate CA and the new intermediate CA.

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