<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ASA DCERPC issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-dcerpc-issue/m-p/4454214#M1083124</link>
    <description>&lt;P&gt;I have the same problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just to confirm:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Do your ACLs explicitly authorize TCP/135?&amp;nbsp; Or are you relying on default Cisco ASA behavior based on interface security levels?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ask because: DCERPC / DCOM-RPC enabled windows applications that communicate with each-other are often uni-directional.&amp;nbsp; E.g., It seems that either host can be the TCP/135 server, accepting the control-connection, and then all the resulting ephemeral TCP ports are independent are independent of the original TCP/135 connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm filing a support request with Cisco now to get an official statement on the status of the &lt;SPAN&gt;&lt;STRONG&gt;dcerpc&lt;/STRONG&gt;&amp;nbsp;inspection engine module.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Aug 2021 15:43:54 GMT</pubDate>
    <dc:creator>BrianSekleckiGE</dc:creator>
    <dc:date>2021-08-24T15:43:54Z</dc:date>
    <item>
      <title>ASA DCERPC issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-dcerpc-issue/m-p/3335236#M970000</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using Nagios to monitor our windows server using WMI. So I configure the DECRPC on our ASA 5520 firewall but i still see the deny on port &amp;gt; 1024.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Below is the configuration:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;class-map MSRPC&lt;BR /&gt;&amp;nbsp;match port tcp eq 135&lt;BR /&gt;!&lt;BR /&gt;policy-map type inspect dcerpc MSRPC-MAP&lt;BR /&gt;&amp;nbsp;description dcerpc inspection for MAP and LOOKUP ops&lt;BR /&gt;&amp;nbsp;parameters&lt;BR /&gt;&amp;nbsp; endpoint-mapper lookup-operation&lt;BR /&gt;&amp;nbsp; timeout pinhole 0:03:00&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class inspection_default&lt;BR /&gt;&amp;nbsp; inspect dns preset_dns_map&lt;BR /&gt;&amp;nbsp; inspect ftp&lt;BR /&gt;&amp;nbsp; inspect h323 h225&lt;BR /&gt;&amp;nbsp; inspect h323 ras&lt;BR /&gt;&amp;nbsp; inspect ip-options&lt;BR /&gt;&amp;nbsp; inspect netbios&lt;BR /&gt;&amp;nbsp; inspect rsh&lt;BR /&gt;&amp;nbsp; inspect rtsp&lt;BR /&gt;&amp;nbsp; inspect sqlnet&lt;BR /&gt;&amp;nbsp; inspect sunrpc&lt;BR /&gt;&amp;nbsp; inspect tftp&lt;BR /&gt;&amp;nbsp; inspect xdmcp&lt;BR /&gt;&amp;nbsp; inspect skinny&lt;BR /&gt;&amp;nbsp; inspect icmp&lt;BR /&gt;&amp;nbsp; inspect dcerpc&lt;BR /&gt;!&lt;BR /&gt;policy-map MSRPC&lt;BR /&gt;&amp;nbsp;class MSRPC&lt;BR /&gt;&amp;nbsp; inspect dcerpc MSRPC-MAP&lt;BR /&gt;!&lt;BR /&gt;service-policy global_policy global&lt;BR /&gt;service-policy MSRPC interface pci-management&lt;BR /&gt;service-policy MSRPC interface pci-external-svcs&lt;/P&gt;
&lt;P&gt;!&lt;/P&gt;
&lt;P&gt;ACL to allow tcp on port 135 is in place as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also tried to use the policy parameter with epm only, and it doesn't work&lt;/P&gt;
&lt;P&gt;I also tried to remove the inspection of dcerpc from global_policy and it's donig the same thing.&lt;/P&gt;
&lt;P&gt;I also tried to only apply the policy-map on the Nagios interface, still the same thing&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone help&amp;nbsp; me out about this please?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:23:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dcerpc-issue/m-p/3335236#M970000</guid>
      <dc:creator>Ge Qu</dc:creator>
      <dc:date>2020-02-21T15:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: ASA DCERPC issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-dcerpc-issue/m-p/4454214#M1083124</link>
      <description>&lt;P&gt;I have the same problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just to confirm:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Do your ACLs explicitly authorize TCP/135?&amp;nbsp; Or are you relying on default Cisco ASA behavior based on interface security levels?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ask because: DCERPC / DCOM-RPC enabled windows applications that communicate with each-other are often uni-directional.&amp;nbsp; E.g., It seems that either host can be the TCP/135 server, accepting the control-connection, and then all the resulting ephemeral TCP ports are independent are independent of the original TCP/135 connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm filing a support request with Cisco now to get an official statement on the status of the &lt;SPAN&gt;&lt;STRONG&gt;dcerpc&lt;/STRONG&gt;&amp;nbsp;inspection engine module.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 15:43:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dcerpc-issue/m-p/4454214#M1083124</guid>
      <dc:creator>BrianSekleckiGE</dc:creator>
      <dc:date>2021-08-24T15:43:54Z</dc:date>
    </item>
  </channel>
</rss>

