Support Center > Search Results > SecureKnowledge Details
"Blocked MS-RPC non compliant version" error in SmartView Tracker Technical Level
  • 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

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".

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