<?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: Allowing RDP into DMZ in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829887#M960545</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it nats it to itself.  you could have just as easily nat'ed it to a dmz IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,dmz) dmz_ip ws-vwright-01&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Nov 2007 19:01:40 GMT</pubDate>
    <dc:creator>srue</dc:creator>
    <dc:date>2007-11-15T19:01:40Z</dc:date>
    <item>
      <title>Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829882#M960540</link>
      <description>&lt;P&gt;When I add a rule for an internal user to rdp into a server in our dmz, the implicit deny does not allow the rule. Below are the rules I currently have for traffic entering the DMZ.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host 172.16.110.4 any eq www &lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host 172.16.110.4 any eq https &lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host 172.16.110.4 any eq ftp &lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host 172.16.110.10 host 10.0.22.229 &lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host 172.16.110.10 host 10.0.22.11 eq www &lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host ws-vwright-01 host 172.16.110.10 eq 3389 &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:31:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829882#M960540</guid>
      <dc:creator>jgorman1977</dc:creator>
      <dc:date>2019-03-11T11:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829883#M960541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so that acl is applied to the dmz interface? egress or ingress?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what pix/asa OS?&lt;/P&gt;&lt;P&gt;is nat-control enabled?&lt;/P&gt;&lt;P&gt;do you have an inside/dmz nat rule for ws-vwright-01?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 18:19:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829883#M960541</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-11-15T18:19:32Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829884#M960542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's an ASA5510.  This is applied on the ingress side.  Nat-control is enabled, but do not have a nat rule for the workstation. Not sure how to implement that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 18:37:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829884#M960542</guid>
      <dc:creator>jgorman1977</dc:creator>
      <dc:date>2007-11-15T18:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829885#M960543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;see if this works:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,dmz) ws-vwright-01 ws-vwright-01&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 18:50:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829885#M960543</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-11-15T18:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829886#M960544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That was it.  Thank you. Does this command just NAT his workstation to a DMZ ip address?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 18:54:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829886#M960544</guid>
      <dc:creator>jgorman1977</dc:creator>
      <dc:date>2007-11-15T18:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829887#M960545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it nats it to itself.  you could have just as easily nat'ed it to a dmz IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,dmz) dmz_ip ws-vwright-01&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 19:01:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829887#M960545</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-11-15T19:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829888#M960546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dynamic NAT (or PAT) is also a possibility. For example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 0 0&lt;/P&gt;&lt;P&gt;global(dmz) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow any machine on the inside (not just one) to access anything on the DMZ.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 19:07:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829888#M960546</guid>
      <dc:creator>elparis</dc:creator>
      <dc:date>2007-11-15T19:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829889#M960547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;his original acl still only allows one host rdp access: ws-vwright-01&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 20:11:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829889#M960547</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-11-15T20:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: Allowing RDP into DMZ</title>
      <link>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829890#M960548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It doesn't matter - the ACE the original poster included is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DMZ extended permit tcp host ws-vwright-01 host 172.16.110.10 eq 3389&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This ACE is not doing anything and can actually be removed - there is no 172.16.110.10 outside of the DMZ network, and since the original poster mentioned this is an ingress ACL ("access-group DMZ in interface DMZ"), this ACE will never be hit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the original poster wants to only allow the machine ws-vwright-01 to contact 172.16.110.10 on TCP port 3398 in the DMZ then an egress ACL on the DMZ interface or an ingress ACL on the inside interface that only allows this flow needs to be applied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As it is right now the original poster can add the dynamic NAT statements that I mentioned and any machine on the inside will be able to RDP into 172.16.110.10, and this without changes to any ACL since traffic from high security interfaces going to lower security interfaces is allowed by default.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 20:28:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/allowing-rdp-into-dmz/m-p/829890#M960548</guid>
      <dc:creator>elparis</dc:creator>
      <dc:date>2007-11-15T20:28:24Z</dc:date>
    </item>
  </channel>
</rss>

