How to fix “DNS_PROBE_Finished_Bad_Config” error
When you are surfing the web and start seeing any strange problems with Chrome especially if you get the dreaded error code “DNS_PROBE_Finished_Bad_Config” many are at a loss of what to do. I was in the same boat and after getting off of it, I decided to help others.
Today I will show you 6 methods which are capable of dealing with the error ‘DNS Probe Finished Bad Config’ in Windows 7 / 8 and 10.
Method 1 – DNS Settings
This method is considered by most techs to be the easiest and best way to solve the problem.
The DNS server that many windows installations choose when they auto config may in fact not be the best one. So, by manually putting the right one in you guarantee that you’ll have the one that is well loved by Chrome.
1. First right click on you ‘Network’ icon and then click ‘Open Network and Sharing Center’.
2. Click on Local area connections. Then click properties.
You will get a new window up. From there you have to select “Internet Protocol Version 4″, and then hit ‘Properties’.
Click on “Use the following DNS Server Addresses” radio button and then in the “Preferred DNS Server” check box type in the following-
188.8.131.52 with the Alternate Server being 184.108.40.206
Last click on “Validate Settings Upon Exit” check box and click Ok. There you have it a great way to fix your Chrome problems with Bad Config.
Method 2 – Resetting IP Catalog
This second method relies on you clearing out the internal catalog of IP addresses. First you need to get into DOS first.
Go to the search box after clicking the Start button and type in “Command Prompt.” You can also access it via the “Accessories” selection on the list of programs. When you get there it quite simple to clear everything out and have windows find the correct IP addresses for itself.
At the command prompt Type “netsh int ip reset” and press “Enter.”
Next Type “netsh winsock reset catalog” Press “Enter”
Windows will now repopulate its catalog and the erring one will be replaced with the correct entry which may fix your problem.
Method 3 – Disabling Firewall and Antivirus
Another thing that can cause your chrome to lose itself is your firewall or Virus protection package. If you receive the error after an upgrade to your virus package or you’ve made changes to your Firewall. This is the first place to look for the possible problem.
So, in this instant shutting off either one first and seeing if the problem clears. If it does you need to roll back to the previous version and contact your vendor for a fix or a workaround.
Method 4 – Getting Rid of Website Filters
If you are running any special software that blocks certain sites or filters them out so members of your household can’t access certain web pages.
If after installation or making changes, your Chrome starts reporting the problem, temporarily disable the software or uninstall it and check for proper operation of your browser.
External Firewalls, such as China’s and Australia’s have been known to cause problems with chrome’s functionality. Purchasing a VPN may cure the problem as well.
Method 5 – Power-cycling Hardware
Hardware can also be the culprit. To check for this, shut down and then unplug your PC/Tablet/Laptop and leave it down for 5 to 10 minutes to ensure that all electricity has discharged from the external power pack. If you are going through a wireless or any other kind of router or DSL box, shut it down as well and leave it off for the same amount of time.
After the wait, power up the Router/DSL box and then the computer and check you websites you were having difficulty with.
Method 6 – Miscellaneous fixes
– Updating you Network driver has been known to fix the problem. Download the latest drivers from vendors websites and install them.
– Delete cookies, Browser Temp files & cache. Deletion of the history file has also been known to correct this problem and so by deleting your browser’s history as well can fix the problem.
– Finally try a different browser, as it may be a Chrome only problem. Firefox, Safari, and IE explorer can all coexist on the same machine and having an alternative browser can help a great deal when attempting to isolate a connection problem such as this one.
If you do in fact, isolate it to Chrome only. Then it may be best to delete the entire browser and reload it from ground zero.Chrome or any of the current browsers are susceptible to error and connection problems. Being able to go through a sequence of different corrective actions can often save you time and the possibility in exacerbating the situation. Noting whether you have changed the software or setting prior to the detection of these kinds of problems such as DNS_PROBE_Finished_Bad_Config yield valuable clues as to which of the 6-Methods we have outlined for you today.
This saves you time in many cases and having to take drastic action to correct problems of this kind. Remember Occam’s Razor and the KISS principle (Keep It Simple, Stupid) with taking the simplest solution first is always the best way to start corrective action.