Netsh winsock reset catalog enter then type: netsh int ip reset reset.log hit enter then reboot. This does solve the problem for a length of time - sometimes for a day, sometimes only a few hours - but then the same issue reoccurs, the browser just goes 'dead' and I have to go through the same process again. It's driving me crazy. TCP/IP Reset in Windows 10 Click the Search icon (magnifying glass) in the bottom left-hand corner. You'll see the Command Prompt app as the best match at the top of the list. A black box with a flashing cursor will open; this is the Command Prompt. Wait for the Command Prompt to run through. Netsh int ip reset resetlog.txt netsh i i r r The last 'r' being the 'log file' that you really don't care to read. What does it do? It hits your TCP/IP stack with a sledge hammer. And forcefully rebuilds it via a rewrite of two Registry keys: SYSTEM CurrentControlSet Services Tcpip Parameters SYSTEM CurrentControlSet Services DHCP Parameters.
![]()
For the past couple of weeks or so (possibly since a recent Win10 update), all my web browsers (Chrome - since uninstalled - and Safari and Edge) lose their internet connections, even though I'm still connected to the internet. After searching for a solution, I have now seen many posts (here and elsewhere) and YouTube videos that advise doing the following:
From an Admin CMD Prompt, type:
netsh winsock reset catalog [enter]
then type:
netsh int ip reset reset.log hit [enter]
then reboot.
This does solve the problem for a length of time - sometimes for a day, sometimes only a few hours - but then the same issue reoccurs, the browser just goes 'dead' and I have to go through the same process again. It's driving me crazy.
What's more, this is now happening on TWO Windows 10 PCs in this household.
On my PC, I originally thought it was an issue with Chrome, so after several uninstalls and reinstalls I left it uninstalled and changed my default browser to Edge. It's made no difference. What's going on?!
So many people seem to have been having the same problem over quite a length of time (going back into 2015 at least) - hence the several YouTube videos on how to fix it - and some seem to find the recommended fix works once and for all, but for me it keeps on occurring. I've run the Troubleshooter over the Network Adapter and no problems are found; I've tried updating the driver(s) but it says I'm using the latest available versions.
Can anyone advise me on any other things I can try? Before I throw both our PCs out the window??
![]()
My PC is:
Acer Aspire M3910
Intel Core i3 CPU 550 @ 3.20GHz
8 GB RAM
64-bit
Netsh Int Ip Reset Windows 10 Windows 10
Windows 10 Pro
Netsh Int Ip Reset Vista
Thanks in advance.
Netsh Int Ip Reset Reset.log Windows 10
OK, just for the sake of answering I will say what I found.
After a lot of trial and error, I figured out what my application did wrong. When I try to configure a network interface with an IP address that was already used by another network interface in the past, first I have to remove that IP configuration for the non-present device and then I can use that IP. To do that I search in every registry in SYSTEMCurrentControlSetServicesTcpipParametersInterfaces and see if any of the interfaces used the IP addres I want to use by comparing the value in 'IPAddress' property with the one I want to use. If I find a match, I first check if that interface is live, and if it's not, I delete the value in 'IPAddress' property and set property 'EnableDHCP' to 1, then I use that IP on my interface. This is what I did wrong. When this interface comes back live again, it will get an IP configuration through DHCP, but it will BSOD if you try to set a static IP on it. The correct way to do it is to set 'IPAddress' property to '0.0.0.0' and 'EnableDHCP' to 1. If you leave 'IPAddress' empty and set 'EnableDHCP' to 1, something goes wrong in IP stack configuration, that 'netsh int ip reset' will fix .. but what exactly it fixes, I have no idea. All I know it's that it's not in the two registries keys that the KB article mentions. Anyway, I'm happy with the resolution I found. I'd wish that this could be done through WinAPI, but unfortunately I had to hack in the registries. P.S.: This problem is present only on Windows 6.1 (Windows 7, Server 2008). Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |