<?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: PIX Natting Problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190815#M605621</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First Thanks for your help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doyou mean .....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 1.1.1.1 10.0.0.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 May 2003 12:25:03 GMT</pubDate>
    <dc:creator>mrcomm2000</dc:creator>
    <dc:date>2003-05-28T12:25:03Z</dc:date>
    <item>
      <title>PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190808#M605614</link>
      <description>&lt;P&gt;Dear All&lt;/P&gt;&lt;P&gt;My network is runnig behind a PIX, i am using a private range of IPs (192.168.100.x) which is distributed through a DHCP server (Also DNS Server) behind the firewall. Every now and then two or three PCs (IPs) stop browsing (accessing the outside world). I have to reboot the PC so that it can work. &lt;/P&gt;&lt;P&gt;When i removed the PIX, and become directly connected to the router everything is working fine and this behavior doesn't happen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any comment ...&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:45:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190808#M605614</guid>
      <dc:creator>mrcomm2000</dc:creator>
      <dc:date>2020-02-21T06:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190809#M605615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems to be an arp-cache related issue. Next time the problem occur, check all the arp caches and make sure they match accross all the pc's and the PIX:&lt;/P&gt;&lt;P&gt;On a W2K pc:   c:\&amp;gt;ipconfig /all (write down the ip and mac addresses)&lt;/P&gt;&lt;P&gt;On the PIX:  pix#sho arp (compare the pc's ip and mac addresses)&lt;/P&gt;&lt;P&gt;On the DHCP server: compare the active leases with the above info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Mustafa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 25 May 2003 14:01:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190809#M605615</guid>
      <dc:creator>mhussein</dc:creator>
      <dc:date>2003-05-25T14:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190810#M605616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does this happen ONLY after a certain numbers of translations(sh xlate)? Check the license for the pix. Should be unrestricted. Are these PC able get out after clearing the translations (clear xlate)? &lt;/P&gt;&lt;P&gt;What is the version on the PIX? Are you PAT'ng or NAT'ng? sh ver and wr t will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;yatin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 25 May 2003 14:14:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190810#M605616</guid>
      <dc:creator>ywadhavk</dc:creator>
      <dc:date>2003-05-25T14:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190811#M605617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First thank you for offering help ...&lt;/P&gt;&lt;P&gt;Second, there is no problem with the licesnse. Honestly i didn't try to run this command (clear xlate) to know if it has an effect or not..&lt;/P&gt;&lt;P&gt;The version : &lt;/P&gt;&lt;P&gt;PIXFIREWALL# sh version&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco PIX Firewall Version 6.2(2)&lt;/P&gt;&lt;P&gt;Cisco PIX Device Manager Version 2.1(1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Compiled on Fri 07-Jun-02 17:49 by morlee&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIXFIREWALL up 1 day 0 hours&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hardware:   PIX-506E, 32 MB RAM, CPU Pentium II 300 MHz&lt;/P&gt;&lt;P&gt;Flash E28F640J3 @ 0x300, 8MB&lt;/P&gt;&lt;P&gt;BIOS Flash AM29F400B @ 0xfffd8000, 32KB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;0: ethernet0:  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&lt;/P&gt;&lt;P&gt;1: ethernet1: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&lt;/P&gt;&lt;P&gt;Licensed Features:&lt;/P&gt;&lt;P&gt;Failover:           Disabled&lt;/P&gt;&lt;P&gt;VPN-DES:            Enabled&lt;/P&gt;&lt;P&gt;VPN-3DES:           Disabled&lt;/P&gt;&lt;P&gt;Maximum Interfaces: 2&lt;/P&gt;&lt;P&gt;Cut-through Proxy:  Enabled&lt;/P&gt;&lt;P&gt;Guards:             Enabled&lt;/P&gt;&lt;P&gt;URL-filtering:      Enabled&lt;/P&gt;&lt;P&gt;Inside Hosts:       Unlimited&lt;/P&gt;&lt;P&gt;Throughput:         Limited&lt;/P&gt;&lt;P&gt;IKE peers:          Unlimited&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am running NATing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 May 2003 09:08:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190811#M605617</guid>
      <dc:creator>mrcomm2000</dc:creator>
      <dc:date>2003-05-27T09:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190812#M605618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PIXFIREWALL# sh run&lt;/P&gt;&lt;P&gt;: Saved&lt;/P&gt;&lt;P&gt;:&lt;/P&gt;&lt;P&gt;PIX Version 6.2(2)&lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;enable password xxxxxxxxx&lt;/P&gt;&lt;P&gt;passwd xxxxxxxxxxxxx encrypted&lt;/P&gt;&lt;P&gt;hostname PIXFIREWALL&lt;/P&gt;&lt;P&gt;domain-name cisco.com&lt;/P&gt;&lt;P&gt;fixup protocol ftp 21&lt;/P&gt;&lt;P&gt;fixup protocol http 80&lt;/P&gt;&lt;P&gt;fixup protocol h323 h225 1720&lt;/P&gt;&lt;P&gt;fixup protocol h323 ras 1718-1719&lt;/P&gt;&lt;P&gt;fixup protocol ils 389&lt;/P&gt;&lt;P&gt;fixup protocol rsh 514&lt;/P&gt;&lt;P&gt;fixup protocol rtsp 554&lt;/P&gt;&lt;P&gt;fixup protocol smtp 25&lt;/P&gt;&lt;P&gt;fixup protocol sqlnet 1521&lt;/P&gt;&lt;P&gt;fixup protocol sip 5060&lt;/P&gt;&lt;P&gt;fixup protocol skinny 2000&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;access-list internal permit tcp any any eq www&lt;/P&gt;&lt;P&gt;access-list internal permit tcp any any eq https&lt;/P&gt;&lt;P&gt;access-list internal permit tcp any any eq pop3&lt;/P&gt;&lt;P&gt;access-list internal permit tcp any any eq smtp&lt;/P&gt;&lt;P&gt;access-list internal permit icmp any any&lt;/P&gt;&lt;P&gt;access-list internal permit udp any any eq domain&lt;/P&gt;&lt;P&gt;access-list internal permit tcp any any eq ftp&lt;/P&gt;&lt;P&gt;access-list internal permit tcp any any eq domain&lt;/P&gt;&lt;P&gt;access-list internal deny ip any any&lt;/P&gt;&lt;P&gt;access-list 101 permit ip 192.168.101.1 255.255.255.0 192.168.101.10 255.255.255.&lt;/P&gt;&lt;P&gt;0&lt;/P&gt;&lt;P&gt;access-list external permit icmp any any&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;logging on&lt;/P&gt;&lt;P&gt;logging trap warnings&lt;/P&gt;&lt;P&gt;logging host inside 192.168.100.1&lt;/P&gt;&lt;P&gt;interface ethernet0 auto&lt;/P&gt;&lt;P&gt;interface ethernet1 auto&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;ip address outside xx.xx.xx.xx 255.255.255.224&lt;/P&gt;&lt;P&gt;ip address inside 192.168.100.x 255.255.255.0&lt;/P&gt;&lt;P&gt;ip audit info action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm&lt;/P&gt;&lt;P&gt;ip local pool pptp-pool 192.168.101.1-192.168.101.10&lt;/P&gt;&lt;P&gt;pdm location 192.168.100.1 255.255.255.255 inside&lt;/P&gt;&lt;P&gt;pdm location 192.168.101.0 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;pdm location 192.168.101.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;pdm location xx.xx.xx.xx 255.255.255.224 outside&lt;/P&gt;&lt;P&gt;pdm location xx.xx.xx.xx 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;pdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (outside) 1 xx.xx.xx.xx&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list 101&lt;/P&gt;&lt;P&gt;nat (inside) 1 192.168.100.0 255.255.255.0 0 0&lt;/P&gt;&lt;P&gt;access-group external in interface outside&lt;/P&gt;&lt;P&gt;access-group internal in interface inside&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 xx.xx.xx.xx 1&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si&lt;/P&gt;&lt;P&gt;p 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ protocol tacacs+&lt;/P&gt;&lt;P&gt;aaa-server RADIUS protocol radius&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;http server enable&lt;/P&gt;&lt;P&gt;http 192.168.101.0 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;http xx.xx.xx.xx 255.255.255.224 outside&lt;/P&gt;&lt;P&gt;http 192.168.100.1 255.255.255.255 inside&lt;/P&gt;&lt;P&gt;no snmp-server location&lt;/P&gt;&lt;P&gt;no snmp-server contact&lt;/P&gt;&lt;P&gt;snmp-server community public&lt;/P&gt;&lt;P&gt;no snmp-server enable traps&lt;/P&gt;&lt;P&gt;floodguard enable&lt;/P&gt;&lt;P&gt;sysopt connection permit-pptp&lt;/P&gt;&lt;P&gt;no sysopt route dnat&lt;/P&gt;&lt;P&gt;crypto map mymap 30 ipsec-isakmp&lt;/P&gt;&lt;P&gt;telnet xx.xx.xx.xx 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;telnet 192.168.101.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;telnet 192.168.100.0 255.255.255.0 inside&lt;/P&gt;&lt;P&gt;telnet timeout 5&lt;/P&gt;&lt;P&gt;ssh timeout 5&lt;/P&gt;&lt;P&gt;vpdn group 1 accept dialin pptp&lt;/P&gt;&lt;P&gt;vpdn group 1 ppp authentication pap&lt;/P&gt;&lt;P&gt;vpdn group 1 ppp authentication chap&lt;/P&gt;&lt;P&gt;vpdn group 1 ppp authentication mschap&lt;/P&gt;&lt;P&gt;vpdn group 1 ppp encryption mppe 40&lt;/P&gt;&lt;P&gt;vpdn group 1 client configuration address local pptp-pool&lt;/P&gt;&lt;P&gt;vpdn group 1 client configuration dns 192.168.100.1&lt;/P&gt;&lt;P&gt;vpdn group 1 pptp echo 60&lt;/P&gt;&lt;P&gt;vpdn group 1 client authentication local&lt;/P&gt;&lt;P&gt;vpdn username test password *********&lt;/P&gt;&lt;P&gt;vpdn enable outside&lt;/P&gt;&lt;P&gt;terminal width 80&lt;/P&gt;&lt;P&gt;Cryptochecksum:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&lt;/P&gt;&lt;P&gt;: end&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no vpdn group 1 accept dialin pptp&lt;/P&gt;&lt;P&gt;no vpdn group 1 ppp authentication pap&lt;/P&gt;&lt;P&gt;no vpdn group 1 ppp authentication chap&lt;/P&gt;&lt;P&gt;no vpdn group 1 ppp authentication mschap&lt;/P&gt;&lt;P&gt;no vpdn group 1 ppp encryption mppe 40&lt;/P&gt;&lt;P&gt;no vpdn group 1 client configuration address local pptp-pool&lt;/P&gt;&lt;P&gt;no vpdn group 1 client configuration dns 192.168.100.1&lt;/P&gt;&lt;P&gt;no vpdn group 1 pptp echo 60&lt;/P&gt;&lt;P&gt;no vpdn group 1 client authentication local&lt;/P&gt;&lt;P&gt;no vpdn username test password *********&lt;/P&gt;&lt;P&gt;no vpdn username sboshra password *********&lt;/P&gt;&lt;P&gt;no vpdn username raya password *********&lt;/P&gt;&lt;P&gt;no vpdn enable outside&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2003 09:34:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190812#M605618</guid>
      <dc:creator>mrcomm2000</dc:creator>
      <dc:date>2003-05-28T09:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190813#M605619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is it possible that you are having a DNS issue. Can the PC's ping by IP address - but not by name. If so, have a look at this bug and try creating a static for your DNS Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSCdy52910 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With multiple recursive DNS servers on the inside that source DNS&lt;/P&gt;&lt;P&gt;query from fix port, such as 53, DNS query can sporadically failed&lt;/P&gt;&lt;P&gt;under high query rate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The workaround is to configure static for the DNS server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's worth a shot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2003 11:27:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190813#M605619</guid>
      <dc:creator>HEATH FREEL</dc:creator>
      <dc:date>2003-05-28T11:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190814#M605620</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;try setting up a syslog server on your internal network  and check if any errors appear in the logging.&lt;/P&gt;&lt;P&gt;To enable syslogging, enter these commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging host ip_address_syslogserver&lt;/P&gt;&lt;P&gt;logging trap 7&lt;/P&gt;&lt;P&gt;logging on&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe level 7 (= debugging) shows too much info and slows down the pix. You can lower the logging level to 4 (=warning) to see dropped packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tom &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2003 12:24:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190814#M605620</guid>
      <dc:creator>tvanginneken</dc:creator>
      <dc:date>2003-05-28T12:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190815#M605621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First Thanks for your help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doyou mean .....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 1.1.1.1 10.0.0.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2003 12:25:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190815#M605621</guid>
      <dc:creator>mrcomm2000</dc:creator>
      <dc:date>2003-05-28T12:25:03Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190816#M605622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, but only if you feel it is a dns issue. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you ping by IP?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2003 18:54:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190816#M605622</guid>
      <dc:creator>HEATH FREEL</dc:creator>
      <dc:date>2003-05-28T18:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190817#M605623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have had the same problem for a long time now so I would like to know if it worked or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, could it come from a bug of the firewall?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any replys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Aug 2003 12:03:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190817#M605623</guid>
      <dc:creator>thomasleroux</dc:creator>
      <dc:date>2003-08-01T12:03:44Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Natting Problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190818#M605624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Honestly, i started the troubleshooting by removing all the access-lists on the Firewall, and in a wiered behavour it seems that everything is fine ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry no solution with technical background ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farouk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Aug 2003 05:42:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-natting-problem/m-p/190818#M605624</guid>
      <dc:creator>mrcomm2000</dc:creator>
      <dc:date>2003-08-03T05:42:36Z</dc:date>
    </item>
  </channel>
</rss>

