Jenkins doesn't recognize a dropped connection

Seemingly randomly Jenkins doesn't recongnize a dropped connection to a rebooting machine. This causes problems for the next build, as it can't attach
to Jenkins, beacuse it still thinks it's connected to the previous build. This then again crashes the new build as Jenkins at some point resets the connection and it somehow still affects this new node which was rejected.

I believe that the rebooted machine actually connects and stays connected enough to start building, but is rejected and Jenkins at this points checks the former connection and resets all the connections causing the build to fail.