<?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: ***************HTTPS RETURN TRAFFIC FROM DMZ**************** in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594744#M591997</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jenn,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Yes, that correct, I did test the same PUBLIC IP by natted it to an IP address in the inside interface address, and it worked fine. As you said the ACL in the outside interface still the same. This server is in 3 different network at the same time: Inside network, DMZ33, DMZ77. DMZ77 is for outside(PUBLIC IP natted to this ) access from Internet, DMZ33 for inside address from the inside network. The NIC connected to the inside network will be shutdown when the server is in production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The default GW is set for the ASA IP( DMZ77 ip in the interface). And ASA can ping the server, server can ping ASA BACK.&lt;/P&gt;&lt;P&gt;2. Server guy said that the personnal firewall of the server is off which may be true as the server is pingable via both its DMZs IP address.&lt;/P&gt;&lt;P&gt;3. I haven't tested the https access yet, but will do that ASAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did do packet capture, the capture show that the FW send the packet out, but the server never respond back(nothing coming back)!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am convince that the server itself is the issue,but I am still need to proove it to the server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jean Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 12 Feb 2011 02:27:22 GMT</pubDate>
    <dc:creator>Jean Paul Enerst</dc:creator>
    <dc:date>2011-02-12T02:27:22Z</dc:date>
    <item>
      <title>***************HTTPS RETURN TRAFFIC FROM DMZ********************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594738#M591988</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I have a server for public access in a DMZ, let's say DMZ10 and the IP for this server is 10.2.3.1. This local IP is natted to a public IP for outside. Packet tracer from in the ASDM shows that the packets get to the host;however, the reply is deny by the default deny any any in the DMZ. I&amp;nbsp; did have the following ACL in the DMZ to permit any https request to the server,but packet still deny... I certainly miss something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DMZxx_access_in line 20 extended permit tcp any host 10.2.3.1 eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:49:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594738#M591988</guid>
      <dc:creator>Jean Paul Enerst</dc:creator>
      <dc:date>2019-03-11T19:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594739#M591992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you please share the configuration of your ASA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have inbound or outbound access-list applied to DMZ10 interface?&lt;/P&gt;&lt;P&gt;If traffic is initiated from outside towards DMZ10 server, the only access-list required is on the outside interface (for inbound direction). You do not need to configure access-list for the return connection as ASA is a stateful firewall (it keeps track of the connection).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if you actually initiate the traffic from DMZ10 server towards the internet/outside, then you require access-list on the DMZ10 interface to allow the traffic outbound (access-list to be applied to dmz10 interface in the inbound direction).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can share the following that would help:&lt;/P&gt;&lt;P&gt;sh run access-group&lt;/P&gt;&lt;P&gt;sh run http&lt;/P&gt;&lt;P&gt;sh run access-list &lt;ACL-NAME-CORRESPOND-TO-THE-OUTPUT-OF-SH-RUN-ACCESS-GROUP-ACL&gt;&lt;/ACL-NAME-CORRESPOND-TO-THE-OUTPUT-OF-SH-RUN-ACCESS-GROUP-ACL&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 01:18:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594739#M591992</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-11T01:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594740#M591993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are the show run commands has requested. As a test, I natted the same Public IP of the server to another local IP inside interface, everything works fine as expected which raise questions in doubt about the DMZ10!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh run access-group&lt;/P&gt;&lt;P&gt;esult of the command: "show run access-group"&lt;/P&gt;&lt;P&gt;access-group Outside_access_in in interface Outside&lt;BR /&gt;access-group Inside_access_in in interface inside&lt;BR /&gt;access-group DMZ10_access_in in interface DMZ10&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;sh run http&lt;/P&gt;&lt;P&gt;Result of the command: "show run http"&lt;/P&gt;&lt;P&gt;http server enable&lt;BR /&gt;http 192.168.1.0 255.255.255.0 management&lt;BR /&gt;http EngLab 255.255.254.0 inside&lt;BR /&gt;http 10.15x.xx.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jean Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 18:49:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594740#M591993</guid>
      <dc:creator>Jean Paul Enerst</dc:creator>
      <dc:date>2011-02-11T18:49:49Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594741#M591994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, that looks good to me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the security level of all the interfaces? Hopefully DMZ10 is not the same as any other interfaces, and higher than the outside interface security level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you perform a "clear xlate" after the changes and modification of NAT statement?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Feb 2011 00:48:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594741#M591994</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-12T00:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594742#M591995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i still need help with this. This server in DMZ can't be accessed fom outside. However, packet tracert from the FW shows the connection in both way(see the attached doc above). When natted the same public ip to another ip in the inside interface, everything works fine... Bebow is part of the configuration..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Version 8.0(4)32 &lt;BR /&gt;!&lt;BR /&gt;dns-guard&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/0&lt;BR /&gt; description Outside connected to MY ISP&lt;BR /&gt; speed 100&lt;BR /&gt; duplex full&lt;BR /&gt; nameif Outside&lt;BR /&gt; security-level 0&lt;BR /&gt; ip address 208.1xx.25x.xx 255.255.xx.224 &lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/1&lt;BR /&gt; speed 100&lt;BR /&gt; duplex full&lt;BR /&gt; nameif inside&lt;BR /&gt; security-level 100&lt;BR /&gt; ip address 10.10.x.x 255.255.255.0 &lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/2&lt;BR /&gt; speed 100&lt;BR /&gt; duplex full&lt;BR /&gt; nameif DMZ33&lt;BR /&gt; security-level 90&lt;BR /&gt; ip address 10.15x.33.x 255.255.255.0 &lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/3&lt;BR /&gt;&amp;nbsp; speed 100&lt;BR /&gt; duplex full&lt;BR /&gt; nameif DMZ77&lt;BR /&gt; security-level 50&lt;BR /&gt; ip address 10.15x.77.x 255.255.255.0 &lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/3&lt;BR /&gt; shutdown&lt;BR /&gt; no nameif&lt;BR /&gt; no security-level&lt;BR /&gt; no ip address&lt;BR /&gt;!&lt;BR /&gt;boot system disk0:/asa804-32-k8.bin&lt;BR /&gt;ftp mode passive&lt;BR /&gt;clock timezone mst -7&lt;BR /&gt;dns server-group DefaultDNS&lt;BR /&gt;same-security-traffic permit inter-interface&lt;BR /&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;access-list DMZ77_access_in extended deny ip DMZ33-Network 255.255.255.0 DMZ77-Network 255.255.255.0 &lt;BR /&gt;access-list DMZ77_access_in extended deny ip DMZ77-Network 255.255.255.0 DMZ33-Network 255.255.255.0 &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Server any eq www &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Server any eq ssh &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Server any eq ftp &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Web-Server any eq ftp &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Web-Server any eq ftp-data &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Web-Server any eq https &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Web-Server any eq 81 &lt;BR /&gt;access-list DMZ77_access_in extended permit tcp host DMZ77-Server-Cust any eq https &lt;BR /&gt;access-list DMZ77_access_in remark *&lt;BR /&gt;access-list Outside_access_in extended permit tcp 208.8x.1x.20x.255.255.224 host 204.xx.xx.xx70 eq www &lt;BR /&gt;access-list Outside_access_in extended permit tcp 208.8x.1x.20x.255.255.224 host 204.xx.xx.xx70 eq ssh &lt;BR /&gt;access-list Outside_access_in extended permit tcp 209.115.232.64 255.255.xx.240 host 204.xx.xx.xx70 eq www &lt;BR /&gt;access-list Outside_access_in extended permit tcp 209.115.232.64 255.255.xx.240 host 204.xx.xx.xx70 eq ssh &lt;BR /&gt;access-list Outside_access_in extended permit ip host 2xx.1xx.1x5.xx host 204.xx.xx.xx&lt;/P&gt;&lt;P&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx70 eq www &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx70 eq ftp&lt;/P&gt;&lt;P&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx71 eq 5222 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx72 eq smtp &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx73 eq ftp &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx73 eq https &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx73 eq www &lt;BR /&gt;access-list Outside_access_in extended permit tcp host 7x.8x.1xx.xx host 204.xx.xx.xx73 eq 81 &lt;BR /&gt;access-list Outside_access_in extended permit tcp host 9x.4x.15x.x0 host 204.xx.xx.xx73 eq 81 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx73 eq ftp-data &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx74 eq ftp &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx74 eq ftp-data &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx74 range 1024 1034 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx70 eq ftp-data &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx75 eq smtp &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx75 eq https &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx75 eq pop3 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx75 eq imap4 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx75 eq 993 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx76 eq www &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx76 eq https &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx77 eq https &lt;BR /&gt;access-list Outside_access_in extended permit icmp any host 204.xx.xx.xx77 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx79 eq ftp &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx79 eq ftp-data &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx80 eq 993 &lt;BR /&gt;access-list Outside_access_in remark Outside Access to New Exchange server&lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx80 eq https &lt;BR /&gt;access-list Outside_access_in remark Outside Access to the New Exchange server&lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx80 eq imap4 &lt;BR /&gt;access-list Outside_access_in remark Outside Access to the new Exchange server&lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx80 eq pop3 &lt;BR /&gt;access-list Outside_access_in extended permit esp any host 204.xx.xx.xx89 &lt;BR /&gt;access-list Outside_access_in extended permit ah any host 204.xx.xx.xx89 &lt;BR /&gt;access-list Outside_access_in extended permit udp any host 204.xx.xx.xx89 eq isakmp &lt;BR /&gt;access-list Outside_access_in extended permit udp any host 204.xx.xx.xx89 eq 4500 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx89 eq 10000 &lt;BR /&gt;access-list Outside_access_in extended permit tcp any host 204.xx.xx.xx93 eq https&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;logging enable&lt;BR /&gt;logging monitor warnings&lt;BR /&gt;logging buffered warnings&lt;BR /&gt;logging asdm informational&lt;BR /&gt;mtu Outside 1500&lt;BR /&gt;mtu inside 1500&lt;BR /&gt;mtu DMZ33 1500&lt;BR /&gt;mtu DMZ77 1500&lt;BR /&gt;mtu management 1500&lt;/P&gt;&lt;P&gt;ip verify reverse-path interface Outside&lt;BR /&gt;ip audit name Inside_Interface attack action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm drop&lt;BR /&gt;no failover&lt;BR /&gt;icmp unreachable rate-limit 1 burst-size 1&lt;BR /&gt;asdm image disk0:/asdm-621.bin&lt;BR /&gt;asdm history enable&lt;BR /&gt;arp timeout 14400&lt;BR /&gt;global (Outside) 10 interface&lt;BR /&gt;global (Outside) 50 204.xx.xx.xx68 netmask 255.255.255.255&lt;BR /&gt;global (Outside) 40 204.xx.xx.xx69 netmask 255.255.255.255&lt;BR /&gt;global (Outside) 20 204.xx.xx.xx66 netmask 255.255.255.255&lt;BR /&gt;global (Outside) 30 204.xx.xx.xx67 netmask 255.255.255.255&lt;BR /&gt;global (DMZ33) 1 DMZ33-Network netmask 255.255.255.0&lt;BR /&gt;nat (inside) 0 access-list inside_nat0_outbound&lt;BR /&gt;nat (inside) 30 EngLab1 255.255.254.0&lt;BR /&gt;nat (inside) 20 EngLab2 255.255.254.0&lt;BR /&gt;nat (inside) 20 EngLab3 255.255.254.0&lt;BR /&gt;nat (inside) 20 EngLab4 255.255.254.0&lt;BR /&gt;nat (inside) 40 0.0.0.0 0.0.0.0&lt;BR /&gt;nat (DMZ33) 1 DMZ33-Network 255.255.255.0&lt;BR /&gt;static (inside,DMZ33) 10.1xx.0.0 10.1xx.0.0 netmask 255.255.0.0&lt;/P&gt;&lt;P&gt;static (inside,Outside) 204.xx.xx.xx75 Server-Dom netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;static (inside,Outside) 204.xx.xx.xx80 Server-Exc netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx72 Server-Kk netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx73 Server-Web netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx71 Server- netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx76 Server-Net netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx70 Server-test netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx78 204.xx.xx.xx78 netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx79 Server-C netmask 255.255.255.255 &lt;BR /&gt;static (inside,Outside) 204.xx.xx.xx93 10.1x.x.24 netmask 255.255.255.255 &lt;BR /&gt;static (DMZ77,Outside) 204.xx.xx.xx77 DMZ77-Server-Cust netmask 255.255.255.255 &lt;BR /&gt;access-group Outside_access_in in interface Outside&lt;BR /&gt;access-group Inside_access_in in interface inside&lt;BR /&gt;access-group DMZ3_access_in in interface DMZ33&lt;BR /&gt;access-group DMZ77_access_in in interface DMZ77&lt;/P&gt;&lt;P&gt;route Outside 0.0.0.0 0.0.0.0 204.xx.xx.xx94 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;route Outside 2.xx.0.0 255.255.0.0 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 2.xx.0.0 255.255.0.0 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 2.xx.0.0 255.255.0.0 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 2.xx.0.0 255.255.0.0 204.xx.xx.xx94 1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;route inside 10.xx.xx.0 255.255.0.0 1x.1xx.0.1 1&lt;/P&gt;&lt;P&gt;route Outside 20x.0.xx.254 194.254 255.255.255.255 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 20x.0.xx.254 204.201 255.255.255.255 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 20x.0.xx.254 209.70 255.255.255.255 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 20x.0.xx.254 209.104 255.255.255.255 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 20x.0.xx.254 209.209 255.255.255.255 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 20x.0.xx.254 209.226 255.255.255.255 204.xx.xx.xx94 1&lt;BR /&gt;route Outside 20x.0.xx.254 220.52 255.255.255.252 204.xx.xx.xx94 1&lt;BR /&gt;route inside 204.xx.xx.xx78 255.255.255.255 1x.1xx.0.1 1&lt;BR /&gt;timeout xlate 3:00:00&lt;BR /&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02&lt;BR /&gt;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00&lt;BR /&gt;timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00&lt;BR /&gt;timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute&lt;BR /&gt;timeout tcp-proxy-reassembly 0:01:00&lt;BR /&gt;dynamic-access-policy-record DfltAccessPolicy&lt;/P&gt;&lt;P&gt;aaa authentication ssh console LOCAL &lt;BR /&gt;http server enable&lt;BR /&gt;http 192.168.1.0 255.255.255.0 management&lt;BR /&gt;http EngLab 255.255.254.0 inside&lt;BR /&gt;http 10.15x.x.0 255.255.255.0 inside&lt;BR /&gt;snmp-server community *****&lt;BR /&gt;snmp-server enable traps snmp authentication linkup linkdown coldstart&lt;BR /&gt;snmp-server enable traps syslog&lt;BR /&gt;crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac &lt;BR /&gt;crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac &lt;BR /&gt;crypto ipsec transform-set TRANS_ESP_3DES_MD5 esp-3des esp-md5-hmac &lt;BR /&gt;crypto ipsec transform-set TRANS_ESP_3DES_MD5 mode transport&lt;BR /&gt;crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac &lt;BR /&gt;crypto ipsec security-association lifetime seconds 28800&lt;BR /&gt;crypto ipsec security-association lifetime kilobytes 4608000&lt;BR /&gt;crypto dynamic-map Outside_dyn_map 20 set transform-set ESP-3DES-SHA&lt;BR /&gt;crypto dynamic-map Outside_dyn_map 40 set transform-set ESP-3DES-SHA&lt;BR /&gt;crypto dynamic-map Outside_dyn_map 60 set transform-set ESP-3DES-SHA&lt;BR /&gt;crypto dynamic-map Outside_dyn_map 80 set transform-set ESP-3DES-SHA&lt;BR /&gt;crypto dynamic-map Outside_dyn_map0 20 set pfs group1&lt;BR /&gt;crypto dynamic-map Outside_dyn_map0 20 set transform-set TRANS_ESP_3DES_MD5&lt;BR /&gt;crypto dynamic-map Outside_dyn_map0 40 set pfs &lt;BR /&gt;crypto dynamic-map Outside_dyn_map0 40 set transform-set ESP-3DES-SHA&lt;BR /&gt;crypto map Outside_map 65535 ipsec-isakmp dynamic Outside_dyn_map&lt;BR /&gt;crypto map VPN_map 65535 ipsec-isakmp dynamic Outside_dyn_map0&lt;BR /&gt;crypto isakmp enable inside&lt;BR /&gt;crypto isakmp policy 10&lt;BR /&gt; authentication pre-share&lt;BR /&gt; encryption 3des&lt;BR /&gt; hash sha&lt;BR /&gt; group 2&lt;BR /&gt; lifetime 28800&lt;BR /&gt;crypto isakmp policy 30&lt;BR /&gt; authentication pre-share&lt;BR /&gt; encryption 3des&lt;BR /&gt; hash md5&lt;BR /&gt; group 2&lt;BR /&gt; lifetime 86400&lt;BR /&gt;crypto isakmp policy 50&lt;BR /&gt; authentication pre-share&lt;BR /&gt; encryption aes&lt;BR /&gt; hash sha&lt;BR /&gt; group 5&lt;BR /&gt; lifetime 86400&lt;BR /&gt;crypto isakmp nat-traversal 90&lt;BR /&gt;client-update enable&lt;BR /&gt;no vpn-addr-assign aaa&lt;BR /&gt;no vpn-addr-assign dhcp&lt;BR /&gt;telnet timeout 5&lt;BR /&gt;ssh 0.0.0.0 0.0.0.0 inside&lt;BR /&gt;ssh EngLabEng 255.255.254.0 inside&lt;BR /&gt;ssh 192.168.1.0 255.255.255.0 management&lt;BR /&gt;ssh timeout 30&lt;BR /&gt;console timeout 0&lt;BR /&gt;dhcpd address 192.168.1.2-192.168.1.254 management&lt;BR /&gt;dhcpd enable management&lt;BR /&gt;!&lt;BR /&gt;threat-detection basic-threat&lt;BR /&gt;threat-detection statistics port&lt;BR /&gt;threat-detection statistics protocol&lt;BR /&gt;threat-detection statistics access-list&lt;BR /&gt;threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200&lt;BR /&gt;ntp server Server-Trivor source inside prefer&lt;BR /&gt;ssl encryption des-sha1 rc4-md5&lt;BR /&gt;class-map inspection_default&lt;BR /&gt; match default-inspection-traffic&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;policy-map type inspect dns migrated_dns_map_1&lt;BR /&gt; parameters&lt;BR /&gt;&amp;nbsp; message-length maximum 512&lt;BR /&gt;policy-map global_policy&lt;BR /&gt; class inspection_default&lt;BR /&gt;&amp;nbsp; inspect dns migrated_dns_map_1 &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 rsh &lt;BR /&gt;&amp;nbsp; inspect rtsp &lt;BR /&gt;&amp;nbsp; inspect esmtp &lt;BR /&gt;&amp;nbsp; inspect sqlnet &lt;BR /&gt;&amp;nbsp; inspect skinny&amp;nbsp; &lt;BR /&gt;&amp;nbsp; inspect sunrpc &lt;BR /&gt;&amp;nbsp; inspect xdmcp &lt;BR /&gt;&amp;nbsp; inspect sip&amp;nbsp; &lt;BR /&gt;&amp;nbsp; inspect netbios &lt;BR /&gt;&amp;nbsp; inspect tftp &lt;BR /&gt;&amp;nbsp; inspect pptp &lt;BR /&gt;&amp;nbsp; inspect dcerpc &lt;BR /&gt;&amp;nbsp; inspect icmp &lt;BR /&gt;&amp;nbsp; inspect http &lt;BR /&gt;policy-map type inspect dns migrated_dns_map_2&lt;BR /&gt; parameters&lt;BR /&gt;&amp;nbsp; message-length maximum 512&lt;BR /&gt;!&lt;BR /&gt;service-policy global_policy global&lt;BR /&gt;prompt hostname context &lt;BR /&gt;: end&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; THANKS,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jean Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Feb 2011 00:54:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594742#M591995</guid>
      <dc:creator>Jean Paul Enerst</dc:creator>
      <dc:date>2011-02-12T00:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594743#M591996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A few things to further troubleshoot the issue:&lt;/P&gt;&lt;P&gt;1) You advised that the same public ip address works fine with a host on the inside --&amp;gt; that means that as far as the public ip address is concern, it is OK.&lt;/P&gt;&lt;P&gt;2) And if it works for an inside host and you just modify the static NAT configuration from inside host to your DMZ host, that means the translation on the ASA is correct too. As long as you issue "clear xlate" after the changes.&lt;/P&gt;&lt;P&gt;3) Then the only access-list required for inbound connection is on the outside interface which refers to the public ip address. So whether you translate the same public ip address to an inside host or to a dmz host, it doesn't really make any difference as far as the access-list is concern. And again, you have tested it working towards an inside host, so it should work just the same for dmz host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All of the above seem to point to the dmz host issue instead of issue on the ASA firewall (again, just to double confirm that as long as you perform "clear xlate" after the changes made from static NAT towards inside host (for your testing) to dmz host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next would be to check the DMZ host itself:&lt;/P&gt;&lt;P&gt;1) What is the default gateway on the host set to? is that the dmz interface ip address of the ASA?&lt;/P&gt;&lt;P&gt;2) Is there any personal firewall, etc enabled that might be blocking inbound connection from different subnets?&lt;/P&gt;&lt;P&gt;3) What about if test HTTP instead of HTTPS connection? Also remember to add access-list on the outside interface (Outside_access_in) for HTTP as I don't see that configured yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lastly, to see exactly where it's failing, you can run packet capture on the ASA (on the dmz interface):&lt;/P&gt;&lt;P&gt;access-list cap-dmz permit ip host &lt;DMZ-HOST-REAL-IP&gt; any&lt;/DMZ-HOST-REAL-IP&gt;&lt;/P&gt;&lt;P&gt;access-list cap-dmz permit ip any host &lt;DMZ-HOST-REAL-IP&gt;&lt;/DMZ-HOST-REAL-IP&gt;&lt;/P&gt;&lt;P&gt;cap cap-dmz interface &lt;DMZ-INTERFACE-NAME&gt; access-list cap-dmz&lt;/DMZ-INTERFACE-NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then try to generate the traffic from the Internet, then check out the output of "sh cap cap-dmz"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Feb 2011 01:16:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594743#M591996</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-12T01:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594744#M591997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jenn,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Yes, that correct, I did test the same PUBLIC IP by natted it to an IP address in the inside interface address, and it worked fine. As you said the ACL in the outside interface still the same. This server is in 3 different network at the same time: Inside network, DMZ33, DMZ77. DMZ77 is for outside(PUBLIC IP natted to this ) access from Internet, DMZ33 for inside address from the inside network. The NIC connected to the inside network will be shutdown when the server is in production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The default GW is set for the ASA IP( DMZ77 ip in the interface). And ASA can ping the server, server can ping ASA BACK.&lt;/P&gt;&lt;P&gt;2. Server guy said that the personnal firewall of the server is off which may be true as the server is pingable via both its DMZs IP address.&lt;/P&gt;&lt;P&gt;3. I haven't tested the https access yet, but will do that ASAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did do packet capture, the capture show that the FW send the packet out, but the server never respond back(nothing coming back)!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am convince that the server itself is the issue,but I am still need to proove it to the server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jean Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Feb 2011 02:27:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594744#M591997</guid>
      <dc:creator>Jean Paul Enerst</dc:creator>
      <dc:date>2011-02-12T02:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: ***************HTTPS RETURN TRAFFIC FROM DMZ****************</title>
      <link>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594745#M591998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is your proof to the server guy:&lt;/P&gt;&lt;P&gt;"I did do packet capture, the capture show that the FW send the packet&amp;nbsp; out, &lt;STRONG&gt;but the server never respond back(nothing coming back)&lt;/STRONG&gt;!"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the server replied back, you should be able to see that in the ASA packet capture because packet capture will show you the packet fresh from the wire.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Feb 2011 04:34:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-return-traffic-from-dmz/m-p/1594745#M591998</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-12T04:34:30Z</dc:date>
    </item>
  </channel>
</rss>

