It's rather irritating.
Rather than "IDK keep sending but I haven't heard ACK in a while"
It's the conceptual equivalent of your phone "helpfully hanging up" when you change the phone from one ear to the other during a call.
Later, Microsoft made it configurable:
https://learn.microsoft.com/en-us/troubleshoot/windows-serve...
Of course if the connection is active when that happens, the other end will probably not like the prolonged silence, and give up first.
1. Remote keeps sending stuff to your unplugged connection
2. You plug your ethernet cable back in
3. Your computer's TCP acknowledges the last sequence number it received for each new sequence it receives from remote
4. Remote sees duplicate ACKs for same sequence number, interprets it as packet loss and resends the stuff
If packets were sent while you were disconnected, they'll be gone, but if you're disconnected for only part of the burst, duplicate ACKing will trigger retransmits.
If you were gone for the whole burst, you'll get put right by timer based retransmits.
If you're gone for long enough, most peers will timeout on unacknowledged data (although that's not in the TCP RFC), and if there's no outstanding data, most peers eventually have some sort of periodic ping and timeout (tcp keep-alives is a reasonable fallback IMHO, if your application protocol doesn't have someything, although the default of IIRC 2 hours feels long in todays world of lots of NATs and much shorter timeouts).