how to troubleshoot pix with the <sackOK>?

Unanswered Question
Apr 26th, 2007

Hi,

I have a problem on connecting to the server from one pc client end. The access list and static already been applied. The capture log shows below:

17:28:17.846101 129.1.16.121.4280 > 10.30.6.142.81: S 1745184384:1745184384(0) win 65535 <mss 1460,nop,nop,sackOK>

17:28:17.846422 10.30.6.142.81 > 129.1.16.121.4280: R 0:0(0) ack 1745184385 win 65535 <mss 1460,nop,nop,sackOK>

17:28:18.257387 119.1.16.121.4280 > 10.10.10.142.81: S 1745184384:1745184384(0) win 65535 <mss 1460,nop,nop,sackOK>

17:28:18.257677 10.10.10.142.81 > 119.1.16.121.4280: R 0:0(0) ack 1745184385 win 65535 <mss 1460,nop,nop,sackOK>

17:28:18.759070 119.1.16.121.4280 > 10.10.10.142.81: S 1745184384:1745184384(0) win 65535 <mss 1460,nop,nop,sackOK>

Please assist what could be the problem on this connection. I can do a ping to the server by granting the icmp request at access-list.

Thanks again.

CIndy

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jon Marshall Thu, 04/26/2007 - 04:47

Hi Cindy

You are getting a Reset back from the server on port 81. Can you confirm that there is a service running on this port ie. telnet to that port from a machine on the same subnet.

Could you also post the static and access-list information from the pix.

Jon

Actions

This Discussion