Solved

ASA5510 Deny TCP ACK over VPN

Posted on 2011-03-01
4
1,100 Views
Last Modified: 2012-05-11
Hi all,

I have this strange issue with VPN.
I have 3 Computers connected to my local network over IPSec Site to Site VPN.

2 of them have Windows XP using IE 7.0
1 of them have  Windows 7 using IE 8.0

I have this really strange issue which occurs intermittently:

One of the PCs (XP) and the other Windows 7 PC seem to have issues loading my web application connected via the VPN.

What I would see it web site found, waiting for reply.
This goes on forever and nothing gets loaded.
While the last PC (XP) has no issues what so ever in loading the web application.

When this happens, i notice this output on the log.

I don't get why this is ONLY happening intermittently or why one of the PCs which is the exact same setup as the other XP machine as well as being part of the exact same network.

Some how from what i understand the ASA is blocking the SYN Handshake of the TCP connection when the client PCs try to connect to my web application server.

192.168.4.21 is the ip of the affected client PC, 10.1.2.50 is the ip of the web application i am running

 
Mar  2 10:35:10 10.1.2.1 %ASA-6-302014: Teardown TCP connection 6719443 for outside:192.168.4.21/1176 to inside:10.1.2.50/80 duration 0:02:06 bytes 8822 TCP Reset-O
Mar  2 10:36:07 10.1.2.1 %ASA-6-302014: Teardown TCP connection 6719800 for outside:192.168.4.21/1178 to inside:10.1.2.51/80 duration 0:01:01 bytes 12155 TCP Reset-I
Mar  2 10:36:54 10.1.2.1 %ASA-6-106015: Deny TCP (no connection) from 192.168.4.21/1178 to 10.1.2.51/80 flags RST ACK  on interface outside
Mar  2 10:39:56 10.1.2.1 %ASA-6-302013: Built inbound TCP connection 6720144 for outside:192.168.4.21/1182 (192.168.4.21/1182) to inside:10.1.2.50/80 (10.1.2.50/80)
Mar  2 10:43:14 10.1.2.1 %ASA-6-302013: Built inbound TCP connection 6720545 for outside:192.168.4.21/1183 (192.168.4.21/1183) to inside:10.1.2.50/80 (10.1.2.50/80)
Mar  2 10:45:45 10.1.2.1 %ASA-6-302013: Built inbound TCP connection 6721021 for outside:192.168.4.21/1187 (192.168.4.21/1187) to inside:10.1.2.50/80 (10.1.2.50/80)
Mar  2 10:45:45 10.1.2.1 %ASA-6-302014: Teardown TCP connection 6720545 for outside:192.168.4.21/1183 to inside:10.1.2.50/80 duration 0:02:35 bytes 14861 TCP Reset-O
Mar  2 10:47:48 10.1.2.1 %ASA-6-302013: Built inbound TCP connection 6721260 for outside:192.168.4.21/1193 (192.168.4.21/1193) to inside:10.1.2.51/80 (10.1.2.51/80)
Mar  2 10:47:49 10.1.2.1 %ASA-6-302014: Teardown TCP connection 6721021 for outside:192.168.4.21/1187 to inside:10.1.2.50/80 duration 0:02:04 bytes 13481 TCP Reset-O
Mar  2 10:48:53 10.1.2.1 %ASA-6-302014: Teardown TCP connection 6721260 for outside:192.168.4.21/1193 to inside:10.1.2.51/80 duration 0:01:05 bytes 6802 TCP Reset-I
Mar  2 10:49:16 10.1.2.1 %ASA-6-106015: Deny TCP (no connection) from 192.168.4.21/1193 to 10.1.2.51/80 flags RST ACK  on interface outside
Mar  2 10:49:18 10.1.2.1 %ASA-6-302013: Built inbound TCP connection 6721356 for outside:192.168.4.21/1195 (192.168.4.21/1195) to inside:10.1.2.50/80 (10.1.2.50/80)
Mar  2 10:51:15 10.1.2.1 %ASA-6-302013: Built inbound TCP connection 6721639 for outside:192.168.4.21/1196 (192.168.4.21/1196) to inside:10.1.2.51/80 (10.1.2.51/80)
Mar  2 10:51:16 10.1.2.1 %ASA-6-302014: Teardown TCP connection 6721356 for outside:192.168.4.21/1195 to inside:10.1.2.50/80 duration 0:02:02 bytes 8822 TCP Reset-O

Open in new window

<--Outside interface Capture-->
   1: 10:32:43.054150 203.169.113.220.57303 > 165.21.83.88.53:  udp 39
   2: 10:32:43.054150 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
   3: 10:32:43.064098 165.21.83.88.53 > 203.169.113.220.57303:  udp 116
   4: 10:32:43.104090 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
   5: 10:32:43.124093 203.169.113.220.57303 > 165.21.83.88.53:  udp 39
   6: 10:32:43.144081 165.21.83.88.53 > 203.169.113.220.57303:  udp 116
   7: 10:32:43.154075 59.198.95.253.22808 > 203.169.113.220.55353:  udp 968
   8: 10:32:43.154075 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
   9: 10:32:43.154075 203.169.113.220.55353 > 59.198.95.253.22808:  udp 52
  10: 10:32:43.154075 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  11: 10:32:43.154075 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  12: 10:32:43.154075 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  13: 10:32:43.204075 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
  14: 10:32:43.224063 59.198.95.253.22808 > 203.169.113.220.55353:  udp 52
  15: 10:32:43.254060 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
  16: 10:32:43.264054 59.198.95.253.22808 > 203.169.113.220.55353:  udp 137
  17: 10:32:43.264054 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  18: 10:32:43.274048 59.198.95.253.22808 > 203.169.113.220.55353:  udp 585
  19: 10:32:43.274048 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  20: 10:32:43.304046 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
  21: 10:32:43.324034 59.198.95.253.22808 > 203.169.113.220.55353:  udp 137
  22: 10:32:43.334043 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  23: 10:32:43.334043 59.198.95.253.22808 > 203.169.113.220.55353:  udp 377
  24: 10:32:43.344037 59.198.95.253.22808 > 203.169.113.220.55353:  udp 52
  25: 10:32:43.344037 115.42.131.170 > 203.169.113.220:  ip-proto-50, length 76
  26: 10:32:43.394022 59.198.95.253.22808 > 203.169.113.220.55353:  udp 137
  27: 10:32:43.394022 203.169.113.220.55353 > 59.198.95.253.22808:  udp 52
  28: 10:32:43.394022 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  29: 10:32:43.394022 59.198.95.253.22808 > 203.169.113.220.55353:  udp 361
  30: 10:32:43.454001 59.198.95.253.22808 > 203.169.113.220.55353:  udp 137
  31: 10:32:43.454001 203.169.113.220.55353 > 59.198.95.253.22808:  udp 52
  32: 10:32:43.454001 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  33: 10:32:43.454001 59.198.95.253.22808 > 203.169.113.220.55353:  udp 361
  34: 10:32:43.474005 59.198.95.253.22808 > 203.169.113.220.55353:  udp 137
  35: 10:32:43.474005 203.169.113.220.55353 > 59.198.95.253.22808:  udp 52
  36: 10:32:43.474005 203.169.113.220.55353 > 59.198.95.253.22808:  udp 105
  37: 10:32:43.474005 59.198.95.253.22808 > 203.169.113.220.55353:  udp 169
  38: 10:32:43.513996 59.198.95.253.22808 > 203.169.113.220.55353:  udp 137

Open in new window

<--Inside interface Capture-->   
1: 10:24:52.162680 10.1.2.50.80 > 192.168.4.21.1195: . 1383111170:1383112550(1380) ack 1290690430 win 6432
   2: 10:25:21.537173 192.168.4.21.1195 > 10.1.2.50.80: R 1290690430:1290690430(0) ack 1383111170 win 0
   3: 10:27:18.523395 192.168.4.21.1197 > 10.1.2.50.80: S 1132117973:1132117973(0) win 65535 <mss 1380,nop,nop,sackOK>
   4: 10:27:18.523395 10.1.2.50.80 > 192.168.4.21.1197: S 849786108:849786108(0) ack 1132117974 win 5840 <mss 1460,nop,nop,sackOK>
   5: 10:27:18.593383 192.168.4.21.1197 > 10.1.2.50.80: . ack 849786109 win 65535
   6: 10:27:18.603377 192.168.4.21.1197 > 10.1.2.50.80: P 1132117974:1132118269(295) ack 849786109 win 65535
   7: 10:27:18.603377 10.1.2.50.80 > 192.168.4.21.1197: . ack 1132118269 win 6432
   8: 10:27:18.603377 10.1.2.50.80 > 192.168.4.21.1197: P 849786109:849786249(140) ack 1132118269 win 6432
   9: 10:27:18.683360 192.168.4.21.1197 > 10.1.2.50.80: P 1132118269:1132118565(296) ack 849786249 win 65395
  10: 10:27:18.693354 10.1.2.50.80 > 192.168.4.21.1197: . 849786249:849787629(1380) ack 1132118565 win 7504
  11: 10:27:18.693354 10.1.2.50.80 > 192.168.4.21.1197: P 849787629:849787959(330) ack 1132118565 win 7504
  12: 10:27:18.783330 192.168.4.21.1197 > 10.1.2.50.80: . ack 849786249 win 65395 <nop,nop,sack sack 1 {849787629:849787959} >
  13: 10:27:18.973292 10.1.2.50.80 > 192.168.4.21.1197: . 849786249:849787629(1380) ack 1132118565 win 7504
  14: 10:27:19.533206 10.1.2.50.80 > 192.168.4.21.1197: . 849786249:849787629(1380) ack 1132118565 win 7504

Open in new window

0
Comment
Question by:jaglin84
  • 2
4 Comments
 
LVL 5

Expert Comment

by:shubhanshu_jaiswal
ID: 35016339
There seems to be a routing issue...could you please post the diagram of your network...
0
 
LVL 6

Expert Comment

by:Galtar99
ID: 35113769
Post the config of the ASA too!
0
 

Accepted Solution

by:
jaglin84 earned 0 total points
ID: 35153606
Hi all,

Thanks for the all the replies, I was away for the past few weeks,
Strangely the problem was automatically resolved.

Thanks!
0
 

Author Closing Comment

by:jaglin84
ID: 35178873
Issue was resolved.
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

Cisco Pix/ASA hairpinning The term, hairpinning, comes from the fact that the traffic comes from one source into a router or similar device, makes a U-turn, and goes back the same way it came. Visualize this and you will see something that looks …
Have you experienced traffic destined through a Cisco ASA firewall disappears and you do not know if the traffic stops in the firewall or somewhere else? The solution is the capture feature. This feature was released in 6.2(1) and works in all firew…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now