After finding the wireshark evidence and backed by your comments, the customer now confirms there is a firewall in the path after all.
Moral of the story - never trust someone's word when troubleshooting.
Just for further reference, the answer is yes: seq/ack numbers should match on both ends...
dcss00, yes the port numbers are the same on both sides of the conversation as well.
Someone else suggested TCP Offload may be to blame. I can't check right now, but believe at least one end of the conversation may have TOE enabled.
Anyone else's thoughts on TOE as a possible cause of what we...
One extra remark. The WAN link is actually a VPN connection. Could that explain things?
It was my understanding a VPN would just encapsulate the TCP/IP packets - or could it modify SEQ/ACK numbers?
kr9,
Thanks for your reply.
The source and destination addresses are indeed the same in the WireShark traces on both ends.
I ran a continuous ping between both sides during the test and based on the location of the ping packets I was able to match the other packets between both wireshark...
I am trying to troubleshoot a dropping network connection between 2 Windows servers on different sides of a WAN connection.
I took wireshark traces on both ends of the conversation and then reproduced the problem.
I'm analyzing the wireshark output, and see different sequence and acknowledge...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.