davesnb
asked on
RST ACK question
Hi All ,
My wireshark trace has only RST ACK , when I filter using display filter tcp.flags.reset==1 . In mostly all instances , the RST , ACk is from source ip - my side . What events can cause this ? Why is there no RST in being found , can I assume the RST is initiated from other side ?
My wireshark trace has only RST ACK , when I filter using display filter tcp.flags.reset==1 . In mostly all instances , the RST , ACk is from source ip - my side . What events can cause this ? Why is there no RST in being found , can I assume the RST is initiated from other side ?
ASKER
in my case the RST/ACK came from third party ip source address, at the same time their error log shows connection exception. However , they then are able to connect soon after. So this is an ongoing intermittent issue. Based on the fact they sent an RST/ACK with no RST can I draw any conclusions on which end the issue is from. or could this be any network device in between?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok will do , thanks
And also, a RST/ACK is not an acknowledgement of a RST. When one side sends the RST, the socket is immediately closed and the other side similarly closes it's socket immediately when receiving the RST.