New
#11
IMO resetting Winsock with netsh winsock reset (and resetting the TCP/IP settings with netsh int ip reset after that, if needed...) could be considered to be above your description of "low-level".
How and Why to Use the Netsh Winsock Reset Command (In 2021)
The order in which to execute the commands has more to do with how it also is possible to try and find clues to what actually was causing the problem. For example, the logical thing to do before ipconfig /release would be something like ipconfig /all >ip-settings-before-release.txt and after ipconfig /renew would be something like ipconfig /all >ip-settings-after-renew.txt to be able to catch a glimpse of what might be going on in that regard. Similarly, you might want to add arp -a >arp-table-before.txt before and arp -a >arp-table-after.txt after arp -d * also in addition to that, just like you could also decide to add ipconfig /displaydns >dns-resolver-cache-before.txt before and ipconfig /displaydns >dns-resolver-cache-after.txt after ipconfig /flushdns and catch more glimpses.