Discussion Locked

TCP/IP syn/ack

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
it is my understanding that for each syn packet there is a resulting ack packet and the ack packet should increment by 1. i have a situation where a w2k server and the clients that connect to it sends the same ack packet for different syn packets. after sending 5 - 10 ack packets without incrementing, it will then add 1 to the next ack packet. i have ruled out looping since the syn packet is different. i guess my question is, is this normal? if not, what would cause this?

3 replies

by some guy in seattle

TCP/IP allows for a process called "windowing" or "sliding windows". This is where the two machines settle on how many data packets will be sent before an ack is returned. The reasoning is that on a good, stable line the chances of data making it through the first time are high, therefore an ack doesn't need to be sent after every packet. Maybe 5, 10, 20 or more packets can be sent before an ack. In the event a packet doesn't make it through, then a request to resend it is sent. Sliding windows is the term used because even after the window size has been settled on, if the link quality changes (up or down) then the whole process of window size agreement can be renegotiated. Bottom line, this is normal.

Hope that helps,

This discussion is closed to new replies.