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

# sk37453 - Connectivity problems on the DCERPC traffic

| Property | Value |
|----------|-------|
| Solution ID | sk37453 |
| Date Created | 2009-03-08 |
| Last Modified | 2017-07-23 |
| Technical Level | Advanced |

## Symptoms

- * Allowing other interfaces beside EPM over port 135 by checking the "Allow DCE-RPC interfaces other than End-Point Mapper (such as DCOM) on Port 135" checkbox under the "DCOM - General Settings" protection will not allow other interfaces beside EPM.
* The "Unallowed UUID in a multi UUID Bind/Alter context request" message in the IPS log.
* If the "MS-RPC - General Settings" protection is set to action Prevent, then the packet will be dropped as well.
* Setting the protection to 'Detect' allows DCOM traffic on port 135, but DCOM protections are not enforced over DCOM traffic.

## Cause

Code limitation in the `$FWDIR/lib/dcom.def` file. If the check for the multiple UUID binds fails, then the Rule Base should be scanned, but it is not.

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