We have an issue that sometimes the client (10.10.10.70) requests a main menu from the server (192.168.1.56), it stucks and the connection times out eventually and the main menu does not get displayed at the client. We did a capture and saw the re-transmission issue as shown in the screenshot below. The server seems to be sending the data back but the client never acknowledges it. Other than the main menu request, the client and the server seem to be communicating properly according to the capture. Any help identifying this issue is greatly appreciated. Thank you
asked 07 Mar '17, 22:16  Khojal |
One Answer:
The capture was probably taken on the server, which is why you have phantom packet sizes larger than 1514 bytes in your file (those never really exist on the network). Please check out this blog post why this can be problematic for troubleshooting: https://blog.packet-foo.com/2014/05/the-drawbacks-of-local-packet-captures/ Other than that, my guess is that you have an MTU problem. Small packets make it through, full packets don't. It's a bit hard to tell because your capture method gives inaccurate results, but it still looks like MTU trouble to me. You might want to check the connection path for the lowest MTU; some device is probably silently blocking big packets. answered 08 Mar '17, 01:52  Jasper ♦♦ |
Thank you Jasper for the feedback. I too suspect the issue could be related to the MTU size. However, when I checked, all MTU sizes that I could see so far are set to 1500. I'm not sure where else could be blocking big packets. Here is how the environment is setup:
Do we still need to adjust the MTU size anywhere in this setup?
How many hops are between client and server? Any router can be blocking the big packets, so you need to check all subnet MTUs between sender and receiver.
If all system resides on one physical machine you can try to update the NIC drivers, as sometimes old drivers have a problem with offloading.