This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

acking each tcp packet

0

Hi Everyone, We have two unix(a & b) servers communicating with each other,basically "a" is application server who sends authentication request to server "b".I can see that both are acking each packet with some data in it.This both servers are across different location and communicating through wan link and due to this frequent ack behaviour it is taking long time to login.Any inputs please.

asked 22 Aug '13, 02:22

kishan%20pandey's gravatar image

kishan pandey
221282936
accept rate: 28%


One Answer:

0

I can see that both are acking each packet with some data in it. due to this frequent ack behaviour it is taking long time to login

" ... with some data in it" - So the client sends a request and gets a response back. And it takes some time (RTT) over the WAN. "... taking a long time to login" - assuming there is only 1 request per login, a single end user should not be waiting too long, unless those authentication requests (or their responses) are queueing up.

Looks like the (auth)-client is serializing all those requests and you suffer from the (longer) latency over the WAN. Maybe Nagle plays a role here also. But I think unless you can change to parallel requests sent to the server, latency will always play a dominant factor here.

answered 23 Aug '13, 05:28

mrEEde's gravatar image

mrEEde
3.9k152270
accept rate: 20%