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

Support Center > Search Results > SecureKnowledge Details

Technical Level

Solution ID	sk66605
Technical Level
Product	Quantum Security Gateways, Quantum Security Management, SmartView Tracker
Version	R77.20, R77.30, R80.10, R80.20, R80.30, R80.40
Platform / Model	All
Date Created	23-Dec-2013
Last Modified	08-Jul-2020

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

Note: To view this solution you need to Sign In .