Hi Jorge, this happens only to this client which is within the subnet 139.96.216.0/24 and also located inside the firewall. Other clients, which are located in other countries but with them same setup (Firewall in front of the WAN connection), doesn't have this problem. I don't think that the problem is caused by congestion-latency, because the response time is ok (less then 100ms).
C:\Documents and Settings\rc3all>ping 121.42.244.12
Pinging 121.42.244.12 with 32 bytes of data:
Reply from 121.42.244.12: bytes=32 time=37ms TTL=121
Reply from 121.42.244.12: bytes=32 time=37ms TTL=121
Reply from 121.42.244.12: bytes=32 time=37ms TTL=121
Reply from 121.42.244.12: bytes=32 time=37ms TTL=121
Ping statistics for 121.42.244.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 37ms, Average = 37ms
I only wanted to be sure that the TCP FIN timeout is not related to the firewall. I think this is because of the application which seems to be not responding!?
