Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Step-by-Step Configuration and Troubleshooting Best Practices for the NGFW, NGIPS and AMP Technologies A Visual Guide to the Cisco Firepower Threat Defense (FTD)
Community Member

Unable to access website

Hi Everyone,

I am trying to access url below here are fw logs from home ASA

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

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)

Aug 13 2013 20:18:41: %ASA-5-304001: 192.168.70.3 Accessed URL 140.98.193.112:http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=01162058&url=http%3A%2F%2Fieeexplore.ieee.org%2Fstamp%2Fstamp.jsp%3Farnumber%3D01162058

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

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)

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

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)

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

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)

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

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)

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

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

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

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)

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

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

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

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

Where 192.168.70.3 is my  pc ip.

Seems to confirm here that above logs tell the issue with specfic url of the website?

Regards

MAhesh

3 ACCEPTED SOLUTIONS

Accepted Solutions

Unable to access website

Hello Mahesh,

It  shows that the session was gracefully shutdown or closed via TCP FIN packets.

If you do a capture asp you should not see any packet..

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

Looks like the FIN packets are being innitiated from the Server side (Way to confirm it is via Packet-Captures my friend)

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC

Unable to access website

Hello Mahesh,

I refered to the captures on pcap format

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.

140.98.193.112.80 > 192.168.71.82.2434: F

That happen after a lot of packets exchanged between those 2 hosts

Can you do

cap asp type asp-drop all circular-buffer

Then attempt to connect and finally provide us the following output

show cap asp | include 140.98.193.112

This will let us know if the ASA is dropping any packets but I honestly do no think so

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC

Unable to access website

Hello,

Any capture that is type asp-drop will basically show the packets being dropped by the ASA.

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.

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
8 REPLIES

Unable to access website

Hello Mahesh,

It  shows that the session was gracefully shutdown or closed via TCP FIN packets.

If you do a capture asp you should not see any packet..

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

Looks like the FIN packets are being innitiated from the Server side (Way to confirm it is via Packet-Captures my friend)

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
Community Member

Unable to access website

Hi Julio,

I will do the packet capture and keep you posted.

Regards

MAhesh

Unable to access website

Hello Mahesh,

Be my guest,

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
Community Member

Unable to access website

Hi Julio,

I have attached the packet capture under the first.

LEt me know which things to look for?

PC  IP  192.168.70.2

Natted IP  192.168.71.82

Regards

Mahesh

Unable to access website

Hello Mahesh,

I refered to the captures on pcap format

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.

140.98.193.112.80 > 192.168.71.82.2434: F

That happen after a lot of packets exchanged between those 2 hosts

Can you do

cap asp type asp-drop all circular-buffer

Then attempt to connect and finally provide us the following output

show cap asp | include 140.98.193.112

This will let us know if the ASA is dropping any packets but I honestly do no think so

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
Community Member

Unable to access website

Hi Julio,

I try that command  output is blank

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

ciscoasa# show cap asp | include 140.98.193.112

What does above command do ?

Regards

MAhesh

Unable to access website

Hello,

Any capture that is type asp-drop will basically show the packets being dropped by the ASA.

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.

Check my blog at http:laguiadelnetworking.com for further information.

Cheers,

Julio Carvajal Segura

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
Community Member

Unable to access website

Thanks Julio for help.

Best Regards

348
Views
0
Helpful
8
Replies
CreatePlease to create content