<?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 Pix firewall in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3065#M674828</link>
    <description>&lt;P&gt;we have a client which have an internal network and they have two interfaces in pix firewall .they also have a web server in internal network and they are using private addresses in network.now problem is any outside user are able to access this web site on web server but when any inside user wants to access the web server it not able to aceess  web server because  in web server we are using private ip address but off course site is mapped with a public/registered ip address so when inside users ping to the actual private ip address of webserver ,it replies but when they ping to public ip address of the hosted web site it gives message "requested time out".I am looking for a solution for this problem.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 05:46:57 GMT</pubDate>
    <dc:creator>achauhan</dc:creator>
    <dc:date>2020-02-21T05:46:57Z</dc:date>
    <item>
      <title>Pix firewall</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3065#M674828</link>
      <description>&lt;P&gt;we have a client which have an internal network and they have two interfaces in pix firewall .they also have a web server in internal network and they are using private addresses in network.now problem is any outside user are able to access this web site on web server but when any inside user wants to access the web server it not able to aceess  web server because  in web server we are using private ip address but off course site is mapped with a public/registered ip address so when inside users ping to the actual private ip address of webserver ,it replies but when they ping to public ip address of the hosted web site it gives message "requested time out".I am looking for a solution for this problem.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:46:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3065#M674828</guid>
      <dc:creator>achauhan</dc:creator>
      <dc:date>2020-02-21T05:46:57Z</dc:date>
    </item>
    <item>
      <title>Re: Pix firewall</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3066#M674851</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We ran into the same problem. I worked around the problem by setting up two internal DNS servers and then pointing all my internal hosts to the internal DNS servers. The internal DNS servers are configured to lookup external addresses for the internal hosts. Anyway, I don't know if this is the best way of doing things but it's working great on my network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2001 13:05:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3066#M674851</guid>
      <dc:creator>rcase</dc:creator>
      <dc:date>2001-02-08T13:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: Pix firewall</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3067#M674877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use the "alias" command to fix the problem.  Depending on where the host and client are (ie DMZ/Inside) the alias command syntax will be different.  A static command also may be required in combination with the alias.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Feb 2001 19:52:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall/m-p/3067#M674877</guid>
      <dc:creator>mb9841</dc:creator>
      <dc:date>2001-02-13T19:52:01Z</dc:date>
    </item>
  </channel>
</rss>

