Admin CMD Prompt - Clean & Reset Network

Hello @hdmi, thanks for the detailed post, it is very much appreciated.

hdmi said:

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.

I do have a Script that I wrote that collects Network information using some 30+ Commands, but the Script is purely for informational purposes [ Link in my signature ].

From an analysis aspect, your method above is indeed an excellent way to narrow down and capture the possible cause[s] of an error, if and when they occur.

I do NOT have a Network problem. The reason the Commands I posted are very few is because the MAIN purpose of my request is to incorporate a Low-Level Network Cleanup as part of my weekly [ or whenever I want to run it ] Cleanup Script.

I might actually leave out the netsh winsock reset Command.

Thanks again.

Hello @hdmi,

I might change the focus of this thread to creating a Script [ which is on my to-do list ] for Network problems using the format that you posted in your previous Post. Something like this for example . . .

Code:

ipconfig /all         > ip-settings-before-release.txt
ipconfig /release
ipconfig /renew
ipconfig /all         > ip-settings-after-renew.txt
arp -a                > arp-table-before.txt
arp -d *
arp -a                > arp-table-after.txt
nbtstat -R
nbtstat -RR
ipconfig /displaydns  > dns-resolver-cache-before.txt
ipconfig /flushdns
ipconfig /displaydns  > dns-resolver-cache-after.txt
ipconfig /registerdns

The files can then be easily compared by using the Compare Plugin in Notepad++, which I find invaluable.

You mentioned previously about using netsh winsock reset and netsh int ip reset. Do you think that they wold be a good addition to the above, and if so, would you place them as the last two entries in the Script above?

Thanks.

Hello @hdmi,

hdmi said:

A suggestion would be to add a pause command so that you can still choose between either letting the script continue or closing the command window. Then when you choose to let it continue, it runs a separate script with the necessary commands to open the before + after (side by side in the plugin for each pair), or something like that.

That can be simply achieved by using . . .

Code:

start Notepad++.exe "%UserProfile%\Desktop\ip-settings-before-release.txt"
start Notepad++.exe "%UserProfile%\Desktop\ip-settings-after-renew.txt"

Code:

@echo off

ipconfig /all     > ip-settings-before-release.txt
ipconfig /release 
ipconfig /renew
ipconfig /all     > ip-settings-after-renew.txt
start Notepad++.exe "%UserProfile%\Desktop\ip-settings-before-release.txt"
start Notepad++.exe "%UserProfile%\Desktop\ip-settings-after-renew.txt"
echo Press ANY key to Continue . . . & pause >nul & taskkill /IM Notepad++.exe /f >nul 2>&1

arp -a   > arp-table-before.txt
arp -d *
arp -a   > arp-table-after.txt
start Notepad++.exe "%UserProfile%\Desktop\arp-table-before.txt"
start Notepad++.exe "%UserProfile%\Desktop\arp-table-after.txt"
echo Press ANY key to Continue . . . & pause >nul & taskkill /IM Notepad++.exe /f >nul 2>&1

nbtstat -R
nbtstat -RR
ipconfig /displaydns > dns-resolver-cache-before.txt
ipconfig /flushdns
ipconfig /displaydns > dns-resolver-cache-after.txt
start Notepad++.exe "%UserProfile%\Desktop\dns-resolver-cache-before.txt"
start Notepad++.exe "%UserProfile%\Desktop\dns-resolver-cache-after.txt"
echo Press ANY key to Continue . . . & pause >nul & taskkill /IM Notepad++.exe /f >nul 2>&1

ipconfig /registerdns
echo Press ANY key to EXIT . . . & pause >nul & Exit

@Paul Black -

A script is just fine, but the network reset process is actually quite simple and straightforward.

Hello @Compumind,

Compumind said:

. . . the network reset process is actually quite simple and straightforward.

Are you talking about a Tutorial, through Settings, or something else? Perhaps you could elaborate please.

Paul Black said:

Hello @Compumind, Are you talking about a Tutorial or something else? Perhaps you could elaborate please.

Unless I'm truly missing something here, I think that your initial procedure (with my input above) is the way to go. Small batch script will do.

Simple as that.

Compumind said:

I think that your initial procedure (with my input above) is the way to go.

Ah, OK, thanks @Compumind.