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

# sk66605 - "Blocked MS-RPC non compliant version" error in SmartView Tracker 

| Property | Value |
|----------|-------|
| Solution ID | sk66605 |
| Date Created | 2012-01-29 |
| Last Modified | 2022-05-24 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server |
| Versions | R81.10 (EOS), R81.10 (EOS) |

## Symptoms

- SmartView log shows: `First tcp135 is allowed, but then the next packet is dropped as "Service_id: RPC-endpoint-mapper-TCP". Information - message_info: Blocked MS-RPC non compliant version`

## Cause

This behavior most commonly occurs because port 135 is being used for RDP or some other service, and this port is normally being reserved for DCE-RPC traffic. The firewall will not recognize that and will generate the log "*Blocked MS-RPC non compliant version*".

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