<?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 DMZ Server access in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920059#M5598</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Enable the HTTPS server to listen on a different port in order to change the configuration that is related to the ASDM service on the ASA, as shown here:&lt;BR /&gt;&lt;PRE&gt;ASA(config)#&lt;STRONG&gt;http server enable &amp;lt;1-65535&amp;gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;configure mode commands/options:&lt;BR /&gt;  &amp;lt;1-65535&amp;gt;  The management server's SSL listening port. TCP port 443 is the&lt;BR /&gt;             default.&lt;/PRE&gt;Here is an example:&lt;BR /&gt;&lt;PRE&gt;ASA(config)#&lt;STRONG&gt;http server enable 65000&lt;/STRONG&gt;&lt;/PRE&gt;&lt;/LI&gt;&lt;LI&gt;After you change the default port configuration, use this format in order to launch the ASDM from a supported web browser on the security appliance network:&lt;BR /&gt;&lt;PRE&gt;&lt;STRONG&gt;https://interface_ip_address:&amp;lt;customized port number&amp;gt;&lt;/STRONG&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Don't forget to permit your public IP to access ASDM with this CLI :&lt;/P&gt;&lt;PRE&gt;&lt;STRONG&gt;http [your public IP] 255.255.255.255 outside&lt;BR /&gt;! or all public IP :&lt;BR /&gt;http 0.0.0.0 0.0.0.0 outside&lt;/STRONG&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;</description>
    <pubDate>Fri, 06 Sep 2019 08:20:10 GMT</pubDate>
    <dc:creator>ssambourg</dc:creator>
    <dc:date>2019-09-06T08:20:10Z</dc:date>
    <item>
      <title>ASA DMZ Server access</title>
      <link>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920053#M5597</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I have one DMZ webserver ( on port 443) in my environment and I want it to use outside interface for PAT.&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;object network DMZ_SERVER_PRIVATE&lt;/P&gt;&lt;P&gt;host 172.16.1.10&lt;/P&gt;&lt;P&gt;nat (dmz, outside) static interface service tcp https https&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Now,&amp;nbsp; I also have https/ASDM access enabled for ASA ( to the box traffic).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When someone tries to connect to my outside IP on 443 how my firewall will know if he's trying to access ASA/ASDM (to the box traffic) or internal WEB server(through the box traffic)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:28:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920053#M5597</guid>
      <dc:creator>umeshunited</dc:creator>
      <dc:date>2020-02-21T17:28:08Z</dc:date>
    </item>
    <item>
      <title>Re: ASA DMZ Server access</title>
      <link>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920059#M5598</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Enable the HTTPS server to listen on a different port in order to change the configuration that is related to the ASDM service on the ASA, as shown here:&lt;BR /&gt;&lt;PRE&gt;ASA(config)#&lt;STRONG&gt;http server enable &amp;lt;1-65535&amp;gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;configure mode commands/options:&lt;BR /&gt;  &amp;lt;1-65535&amp;gt;  The management server's SSL listening port. TCP port 443 is the&lt;BR /&gt;             default.&lt;/PRE&gt;Here is an example:&lt;BR /&gt;&lt;PRE&gt;ASA(config)#&lt;STRONG&gt;http server enable 65000&lt;/STRONG&gt;&lt;/PRE&gt;&lt;/LI&gt;&lt;LI&gt;After you change the default port configuration, use this format in order to launch the ASDM from a supported web browser on the security appliance network:&lt;BR /&gt;&lt;PRE&gt;&lt;STRONG&gt;https://interface_ip_address:&amp;lt;customized port number&amp;gt;&lt;/STRONG&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Don't forget to permit your public IP to access ASDM with this CLI :&lt;/P&gt;&lt;PRE&gt;&lt;STRONG&gt;http [your public IP] 255.255.255.255 outside&lt;BR /&gt;! or all public IP :&lt;BR /&gt;http 0.0.0.0 0.0.0.0 outside&lt;/STRONG&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2019 08:20:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920059#M5598</guid>
      <dc:creator>ssambourg</dc:creator>
      <dc:date>2019-09-06T08:20:10Z</dc:date>
    </item>
    <item>
      <title>Re: ASA DMZ Server access</title>
      <link>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920216#M5599</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thank you for your reply.&lt;/P&gt;&lt;P&gt;But the thing is that I implemented this in GNS and it showed that it directed that connection to DMZ server.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why the firewall did not consider it as to the box traffic?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WEB_PRIV----- (dmz) [ASA](outside)----- outside router&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have trimmed the output to show only relevant info.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ciscoasa# show run http&lt;BR /&gt;http server enable&lt;BR /&gt;http 10.0.0.0 255.255.255.0 inside&lt;BR /&gt;http 0.0.0.0 0.0.0.0 outside&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ciscoasa# show ip&lt;BR /&gt;System IP Addresses:&lt;BR /&gt;Interface Name IP address Subnet mask Method&lt;BR /&gt;GigabitEthernet0/0 outside 20.0.0.1 255.255.255.0 CONFIG&lt;BR /&gt;GigabitEthernet0/1 inside 10.0.0.1 255.255.255.0 CONFIG&lt;BR /&gt;GigabitEthernet0/2 dmz 172.16.0.1 255.255.255.0 CONFIG&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ciscoasa# sho run object&lt;BR /&gt;object network WEB_PRIV&lt;BR /&gt;host 172.16.0.5&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ciscoasa# show run nat&lt;BR /&gt;!&lt;BR /&gt;object network WEB_PRIV&lt;BR /&gt;nat (dmz,outside) static interface service tcp https https&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ciscoasa# show run access-list&lt;/P&gt;&lt;P&gt;access-list OUTSIDE_IN extended permit tcp any object WEB_PRIV eq https&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;outside_router#telnet 20.0.0.1 443&lt;BR /&gt;Trying 20.0.0.1, 443 ... Open&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WEB_PRIV#show tcp brief&lt;BR /&gt;TCB&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Local Address&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Foreign Address&amp;nbsp; &amp;nbsp; &amp;nbsp;(state)&lt;BR /&gt;65496C80&amp;nbsp; &amp;nbsp; &amp;nbsp; 172.16.0.5.443&amp;nbsp; &amp;nbsp; &amp;nbsp; 20.0.0.10.29126&amp;nbsp; &amp;nbsp; &amp;nbsp; ESTAB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2019 14:10:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-dmz-server-access/m-p/3920216#M5599</guid>
      <dc:creator>umeshunited</dc:creator>
      <dc:date>2019-09-06T14:10:39Z</dc:date>
    </item>
  </channel>
</rss>

