How do I figure out why my PC is sending RST, ACK?
I don't believe the application is sending it. Sorry I'm fairly new to Wireshark's functions.
I think the client sent the RST, ACK as a "fast" way to terminate the connection after ~9.5s of no traffic on the 56932 - 443 connection.
The same client then initiates a new connection (source port 56962) after ~6.3 seconds.
As noted above in the comments, determining why this occurs would require knowledge of the client application, hopefully supported by application logs.
Asked: 2025-01-02 13:06:04 +0000
Seen: 48 times
Last updated: yesterday
Wireshark is not able to tell you WHY a session gets a RST. But in this case it seems the client is done and starts a new session after about 5 to 6 seconds.
More details need to come from your client or server application logs. You may need to enable debugging or something like that. But what ever application so ever sends a RST packet on an open TCP connection is reponsible for logging why it did so. You won't be able to tell from an empty packet.
But the RST ACK might be because there is no data for 3 seconds. Which is relative long in computer terms.