 | 1 | initial version |
If I look with a filter like "tcp.port == 43188" then I am suddenly reminded about 2MSL issues.
While the timing does not warrant it as I have never seen an issue before where a re-use of a port combinaton is an issue after 120 seconds silence. The results seem to indicate that the server might have an issue there.
I would focus on port re-usage issues for now.
| | 2 | No.2 Revision |
If I look with a filter like "tcp.port == 43188" then I am suddenly reminded about 2MSL issues.
While the timing does not warrant it as I have never seen an issue before where a re-use of a port combinaton is an issue after 120 seconds silence. The results seem to indicate that the server might have an issue there.
I would focus on port re-usage issues for now.
If you have access to the server you may also want to look at the output of netstat -nat and see if you have Time-Wait for a long time on the port where you don't get the expected SYN-ACK response.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
