<?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: Access to services on the DMZ while VPN'd in in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060522#M895175</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most likely you are just missing nat exemption. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz_nat0_outbound extended permit ip any &lt;VPN.CLIENT.SUBNET&gt;&lt;/VPN.CLIENT.SUBNET&gt;&lt;/P&gt;&lt;P&gt;nat (dmz) 0 access-list dmz_nat0_outbound&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Oct 2008 12:02:41 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2008-10-13T12:02:41Z</dc:date>
    <item>
      <title>Access to services on the DMZ while VPN'd in</title>
      <link>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060520#M895168</link>
      <description>&lt;P&gt;I have a Cisco 5510 that has a DMZ setup on it and supports Remote Access via the legacy client, not web or SSL. While on VPN I can get to all internal resources, have no problems. However I cannot conect to any resouce in the Dmz. I've look at the Nat rules and firewall rules, however I am stumped.  I think the order of operations is the VPN packet arrives at the outside interface, ACLs are checked, then decrypted, then Nat'd (if any) and the passed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I am assuming i need to have rules that allow the decrypted packet traverse from the Outside interface to the Dmz and back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I am not sure how to go about this.  The address I am trying to reach in the DMZ is the actual address of the webserver and not its Nat'd address.&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;Randy&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:56:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060520#M895168</guid>
      <dc:creator>moorera</dc:creator>
      <dc:date>2019-03-11T13:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: Access to services on the DMZ while VPN'd in</title>
      <link>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060521#M895172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you post your config and maybe that will shed some light on it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What type of service does the Server on DMZ supply?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 11:23:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060521#M895172</guid>
      <dc:creator>jstabl</dc:creator>
      <dc:date>2008-10-13T11:23:58Z</dc:date>
    </item>
    <item>
      <title>Re: Access to services on the DMZ while VPN'd in</title>
      <link>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060522#M895175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most likely you are just missing nat exemption. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz_nat0_outbound extended permit ip any &lt;VPN.CLIENT.SUBNET&gt;&lt;/VPN.CLIENT.SUBNET&gt;&lt;/P&gt;&lt;P&gt;nat (dmz) 0 access-list dmz_nat0_outbound&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 12:02:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060522#M895175</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-10-13T12:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: Access to services on the DMZ while VPN'd in</title>
      <link>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060523#M895177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the post. That is what I thought but still no joy.... WOuld you perhaps know from what interface would the PIX think this request originates from. My thought is since the traffic comes through the Outside interface, is deencrypted and then placed in the inside interface que that perhaps there is no way to bounce this traffic to the DMZ interface as it would be entering the interface (inside) to get there form where it is from.  I'm thinking this is not allowed (normally isn't) and I cannot think of how to make this work..... THoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 14:23:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060523#M895177</guid>
      <dc:creator>moorera</dc:creator>
      <dc:date>2008-10-13T14:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: Access to services on the DMZ while VPN'd in</title>
      <link>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060524#M895178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are using a legacy client is it setup to use the default gateway on the remote network? Nothing to do with the asa itself but how the vpn is handling routing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2008 21:33:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-to-services-on-the-dmz-while-vpn-d-in/m-p/1060524#M895178</guid>
      <dc:creator>sjones1966</dc:creator>
      <dc:date>2008-10-13T21:33:31Z</dc:date>
    </item>
  </channel>
</rss>

