<?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: Configuration Issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/configuration-issue/m-p/997960#M939741</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though ithe problem is not very much clear from your post, I am replying what I understood.&lt;/P&gt;&lt;P&gt;You have to configure NAT for that,either static or PAT.In ASA there is a default NAT-CONTROL.This means every ip wats to pass through pix/ASA , needs a nat rule.Fot PAT configure this:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;nat(dmz_int)1 1.1.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;global(outside_int)1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By giving this commands your internal servers can access outside(internet).But if you want outsiders also access your server ,you hane to configure static nat.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 05 Apr 2008 07:00:05 GMT</pubDate>
    <dc:creator>abhisheksen</dc:creator>
    <dc:date>2008-04-05T07:00:05Z</dc:date>
    <item>
      <title>Configuration Issue</title>
      <link>https://community.cisco.com/t5/network-security/configuration-issue/m-p/997959#M939738</link>
      <description>&lt;P&gt;Hi, We are using ASA FW and all configuration is setup properly but we have an issue but we are not sure is it required any configuration on FW or its a conf issue. DMZ machines and Internal DB machines are getting access wach other fine and one of www (web Server) is in DMZ zone and enable static nating for outside users and map dns (A) host entry with the public IP like &lt;A class="jive-link-custom" href="http://www.yahoo.com" target="_blank"&gt;www.yahoo.com&lt;/A&gt; and map this url with public ip 22.22.22.22 and this public ip map with local ip 1.1.1.1 by natting and outside users are able to access this app fine but the other server 1.1.1.2 (loacl Ip) try to access the app like &lt;A class="jive-link-custom" href="http://www.yahoo.com" target="_blank"&gt;www.yahoo.com&lt;/A&gt; then it doent work but when it tries to resolve yahoo web site by local ip 1.1.1.1 then it works fine. Can anyone tell us is it a conf issue if it is then what must we do?? Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:27:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/configuration-issue/m-p/997959#M939738</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2019-03-11T12:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: Configuration Issue</title>
      <link>https://community.cisco.com/t5/network-security/configuration-issue/m-p/997960#M939741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though ithe problem is not very much clear from your post, I am replying what I understood.&lt;/P&gt;&lt;P&gt;You have to configure NAT for that,either static or PAT.In ASA there is a default NAT-CONTROL.This means every ip wats to pass through pix/ASA , needs a nat rule.Fot PAT configure this:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;nat(dmz_int)1 1.1.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;global(outside_int)1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By giving this commands your internal servers can access outside(internet).But if you want outsiders also access your server ,you hane to configure static nat.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Apr 2008 07:00:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/configuration-issue/m-p/997960#M939741</guid>
      <dc:creator>abhisheksen</dc:creator>
      <dc:date>2008-04-05T07:00:05Z</dc:date>
    </item>
  </channel>
</rss>

