<?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 Unable to access website in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293390#M344754</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will do the packet capture and keep you posted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Aug 2013 04:35:02 GMT</pubDate>
    <dc:creator>mahesh18</dc:creator>
    <dc:date>2013-08-14T04:35:02Z</dc:date>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293388#M344752</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to access url below here are fw logs from home ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305011: Built dynamic TCP translation from DMZ:192.168.70.3/1360 to outside:192.168.71.2/1360&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302013: Built outbound TCP connection 17717 for outside:140.98.193.112/80 (140.98.193.112/80) to DMZ:192.168.70.3/1360 (192.168.71.2/1360)&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Aug 13 2013 20:18:41: %ASA-5-304001: 192.168.70.3 Accessed URL 140.98.193.112:&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://ieeexplore.ieee.org/xpl/login.jsp?tp=&amp;amp;arnumber=01162058&amp;amp;url=http%3A%2F%2Fieeexplore.ieee.org%2Fstamp%2Fstamp.jsp%3Farnumber%3D01162058" rel="nofollow" target="_blank"&gt;http://ieeexplore.ieee.org/xpl/login.jsp?tp=&amp;amp;arnumber=01162058&amp;amp;url=http%3A%2F%2Fieeexplore.ieee.org%2Fstamp%2Fstamp.jsp%3Farnumber%3D01162058&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305011: Built dynamic TCP translation from DMZ:192.168.70.3/1361 to outside:192.168.71.2/1361&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302013: Built outbound TCP connection 17718 for outside:140.98.193.169/80 (140.98.193.169/80) to DMZ:192.168.70.3/1361 (192.168.71.2/1361)&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305011: Built dynamic TCP translation from DMZ:192.168.70.3/1362 to outside:192.168.71.2/1362&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302013: Built outbound TCP connection 17719 for outside:208.92.236.82/80 (208.92.236.82/80) to DMZ:192.168.70.3/1362 (192.168.71.2/1362)&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305011: Built dynamic TCP translation from DMZ:192.168.70.3/1363 to outside:192.168.71.2/1363&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302013: Built outbound TCP connection 17720 for outside:140.98.193.169/80 (140.98.193.169/80) to DMZ:192.168.70.3/1363 (192.168.71.2/1363)&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305011: Built dynamic TCP translation from DMZ:192.168.70.3/1364 to outside:192.168.71.2/1364&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302013: Built outbound TCP connection 17721 for outside:140.98.193.112/443 (140.98.193.112/443) to DMZ:192.168.70.3/1364 (192.168.71.2/1364)&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302014: Teardown TCP connection 17719 for outside:208.92.236.82/80 to DMZ:192.168.70.3/1362 duration 0:00:00 bytes 1421 TCP FINs&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305012: Teardown dynamic TCP translation from DMZ:192.168.70.3/1362 to outside:192.168.71.2/1362 duration 0:00:00&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-305011: Built dynamic TCP translation from DMZ:192.168.70.3/1365 to outside:192.168.71.2/1365&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:41: %ASA-6-302013: Built outbound TCP connection 17722 for outside:140.98.193.112/443 (140.98.193.112/443) to DMZ:192.168.70.3/1365 (192.168.71.2/1365)&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:47: %ASA-6-302014: Teardown TCP connection 17722 for outside:140.98.193.112/443 to DMZ:192.168.70.3/1365 duration 0:00:05 bytes 415 TCP FINs&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:47: %ASA-6-305012: Teardown dynamic TCP translation from DMZ:192.168.70.3/1365 to outside:192.168.71.2/1365 duration 0:00:05&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:47: %ASA-6-302014: Teardown TCP connection 17720 for outside:140.98.193.169/80 to DMZ:192.168.70.3/1363 duration 0:00:05 bytes 0 TCP FINs&lt;/P&gt;&lt;P&gt;Aug 13 2013 20:18:47: %ASA-6-305012: Teardown dynamic TCP translation from DMZ:192.168.70.3/1363 to outside:192.168.71.2/1363 duration 0:00:05&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where 192.168.70.3 is my&amp;nbsp; pc ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Seems to confirm here that above logs tell the issue with specfic url of the website?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:25:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293388#M344752</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T02:25:24Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293389#M344753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It&amp;nbsp; shows that the session was gracefully shutdown or closed via TCP FIN packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do a capture asp you should not see any packet..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Teardown TCP connection 17719 for outside:208.92.236.82/80 to DMZ:192.168.70.3/1362 duration 0:00:00 bytes 1421 &lt;STRONG&gt;TCP FINs&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks like the FIN packets are being innitiated from the Server side (Way to confirm it is via Packet-Captures my friend)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check my blog at http:laguiadelnetworking.com for further information. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2013 03:29:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293389#M344753</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-08-14T03:29:48Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293390#M344754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will do the packet capture and keep you posted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2013 04:35:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293390#M344754</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-08-14T04:35:02Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293391#M344755</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Be my guest,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check my blog at http:laguiadelnetworking.com for further information. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2013 04:36:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293391#M344755</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-08-14T04:36:33Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293392#M344756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached the packet capture under the first.&lt;/P&gt;&lt;P&gt;LEt me know which things to look for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PC&amp;nbsp; IP&amp;nbsp; 192.168.70.2&lt;/P&gt;&lt;P&gt;Natted IP&amp;nbsp; 192.168.71.82&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 02:12:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293392#M344756</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-08-15T02:12:50Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293393#M344757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I refered to the captures on pcap format &lt;SPAN __jive_emoticon_name="grin" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/grin.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But here is the interesting fact based on that capture: On packet 135 we can see the server gracefully closing the connection with a FIN packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 140.98.193.112.80 &amp;gt; 192.168.71.82.2434: F&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That happen after a lot of packets exchanged between those 2 hosts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you do&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cap asp type asp-drop all circular-buffer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then attempt to connect and finally provide us the following output &lt;/P&gt;&lt;P&gt;show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will let us know if the ASA is dropping any packets but I honestly do no think so &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check my blog at http:laguiadelnetworking.com for further information. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 03:55:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293393#M344757</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-08-15T03:55:12Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293394#M344759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I try that command&amp;nbsp; output is blank&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;ciscoasa# show cap asp | include 140.98.193.112&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does above command do ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 04:40:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293394#M344759</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-08-15T04:40:54Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293395#M344761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any capture that is type asp-drop will basically show the packets being dropped by the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case we can see that the ASA is not the one dropping the traffic so there is some reason out of the scope of the ASA (On the server side) that is causing the server to close gracefully the connection with a FIN packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check my blog at http:laguiadelnetworking.com for further information. &lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 05:22:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293395#M344761</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-08-15T05:22:13Z</dc:date>
    </item>
    <item>
      <title>Unable to access website</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293396#M344764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Julio for help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Aug 2013 00:41:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-access-website/m-p/2293396#M344764</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-08-16T00:41:20Z</dc:date>
    </item>
  </channel>
</rss>

