The first time this happened to my PC the "netsh int ipv4 install " in command prompt worked just fine, which I thank Efta for.
A couple of weeks later the same problem arose. The same command did not work.
However this did:
netsh winsock reset catalog
netsh int ip reset
ipconfig /flushdns
Thank you Arthur and Efta for the solutions!
Hi guys,
I have followed instructions from here to tackle this problem and they used to work but not anymore.
"Short" recap:
1. First I had the problem one or more network protocols are missing and it was fixed using the netsh int ip reset c:\resetlog.txt command after editing registery so that I gave full rights in NSI folder 26.
2. I had to repeat following few times but it did fix the problem everytime
3. About one week or so from the first problem I had another problem along the missing protocol. The problem was the winsock problem which was fixed when I resetted the winsock by using the command: netsh winsock reset along with the command netsh int ip reset. That fixed any issues
4. Now both of those problems came back with additional problem network adapter. I have tried every fix there is also those which used to work but now nothing is fixing this issue. Everytime I reboot the computer the tap from the registery NSI folder 26 where I grant full rights to everybody goes away thus making the netsh int ip reset fix unable to work I guess? Is there any way make sure that the tap in the registery stays on? Any other suggestion?
5. I have disabled Internet Protocol Version 6 (TCP/IPv6) and NetBIOS TCP/IP, used command netsh int ipv4 install and tried this:
netsh winsock reset catalognetsh int ip reset
ipconfig /flushdns
6. My hardware is Dell XPS 13 2015 and only wifi.
Had this error occurring. Then had it on 2 computers.
Saw a suggestion to plug computer directly into the router not via any ethernet other than the single cable.
Both computers worked.
Problem was identified as using a faulty Homeplug AV (Powerline adapter)
When I swapped for a working one all was OK.
Why the error message indicates that something was wrong with my computer I do not know.
I then bought a couple more from local store for £25 /pair
Now both computers working with powerline.
If you do not use powerline, maybe this will give you some sort of a clue to look at the network cabling. As someone suggested (which saved me throwing things out the window) try connecting to router first and see if that helps.
If you have an intermittent fault it could be a cable or adapter or something in your network is occasionally failing ?
Good Luck
OK so disabling ipv 6 and using 4 seems to have partly solved this. However this is the 3rd time I've attempted to post this reply.
Wouldn't it be better to find out which protocol was missing and install it, though? Then I could use 6
So I just encountered this issue, and searched for a solution on my phone (WiFi was still up, computer just couldn't connect). I figured it out, mostly thanks to this forum, and I thought I would list what I did that didn't work, and what finally did.
What didn't work:
--Windows troubleshoot network problems (no surprise there)
--sfc /scannow
--netsh winsock reset catalog
netsh int ip reset
ipconfig /flushdns
--remove the tick next to 'Internet Protocol Version 6 (TCP/IPv6 )' in adapter settings
--netsh int ipv4 install
--netsh winsock reset catalog
netsh int ip reset
ipconfig /flushdns
What did:
I went to my Network Connections, right-clicked on my Local Area Connection, clicked Properties, selected Internet Protocol Version 4 (TCP/IPv4), clicked Properties, and selected both 'Obtain an IP address automatically' buttons.
Changing that immediately allowed my computer to connect, and the first thing I did was come here, make an account, and post this. For those still having this issue, might be worth a shot.
Got the same problem on a brand new Lenovo after 1511 update was installed on March 3.
I rolled back the install to check the problem went away (it did and I could instantly get on line again). I then switched to scheduled updates and downloaded 1511 again, once downloaded I disconnected my wifi and then disabled my AVG firewall and then selected install updates and shut down so that 1511 was installed again.
Once back up, all was good and I could connect to the internet again and so I've re-enabled my AVG firewall. So far so good.
The AVG might be a red herring and simply rolling back 1511 and then re-installing it may also do the trick.
Certainly no need to disable TCP/IP v6, or re-install it. Also no need to run any winsocks commands etc. Obviously every case is the different as can be seen by the many different solutions but this worked well for me, was easy and hopefully will help someone else
I tried this fix with my Windows 10 update, but no joy.
After reverting back to Windows 7, doing multiple attempts at other fixes, completing what seemed to be possibly an incomplete update application (crazy how these partial bits and pieces accumulate), and still getting no success, I tried this fix once again, restarted, and suddenly it worked.
Now I'm pushing my luck and trying to install Windows 10 again. :) At least I know I can repeat at least some of the above steps and get things back. I really would like to upgrade and I really would like internet connectivity!
But thanks, efta, for your fix. I had to fix some other things to enable the fix--at least, I guess that's what I did, who knows?--but in the end it was your advice that helped me go the last mile. So THANKS.
Quick update:
Installed Windows 10 again, problem recurred.
This time, two additional steps for a fix:
1. Turned Windows Firewall off -- theory: might conflict with AVG antivirus. This one seems a stretch, but I record it for completeness.
2. Went to adapter properties and made sure every possible installable protocol was installed. You can get the list by clicking on any protocol to highlight it, selecting install, selecting protocol, then installing every protocol you see there.
Having done these things, I restarted, with no luck.
THEN I ran efta's script again, and connectivity came back, for the first time in my attempt to upgrade to Windows 10.
FWIW, YMMV -- and thanks again to efta's initial suggestion as well as to all the informed and helpful discussion in this thread.
Quote