DNS server not responding to Windows 10

[medsec222]

Thanks Frank - I will do that tomorrow when my mind is fresh. Thank you for all your expert help. Kind regards.

[Workingman]

Like I have got lots of other things to do in these pressing times apart from drink voddy and watch Netflix.

It has actually been good for the old grey matter, so thanks to you too.

Now, where's me glass?

[medsec222]

Hi Frank - I got as far as ping BBC.co.uk and pressed enter but it just brought me back to C:\Users etc.

[Workingman]

OK, sort of expected, now try C:\Users\name>ipconfig

I am looking to see at least one adaptor in working order.

[Workingman]

Meds, we are going into T 3 here from midnight and I have one last visit to make later on - you'll know what I am on about as you are already there. So, what I will do is send you some stuff via PM which you can run through at your leisure. Catch you later.

[medsec222]

Thank you Frank

[Workingman]

PM sent. will catch you later.

[Suff]

Sorry was busy all weekend.

Instead of running ping, I would have run nslookup. You can type nslookup and press enter. Once it is started, nslookup will tell you the DNS server you are using and the IP address. Mine is 192.168.1.1.

If that doesn't produce an error, you can type in an address like www.bbc.co.uk and it will either tell you that it has found the address or it will throw an error.

You can also change DNS servers, AS WM suggested. If you type

SERVER 8.8.8.8 and press enter, it should return and tell you the server is ready.

If, at any time, the DNS tells you it has a problem finding the server (Time Out etc), then you have a problem.

Other things I would do with a computer which was working.

In the same command window type

ipconfig /release press enter
ipconfig /renew press enter

It is usually something small which causes these problems.

The other thing to do is reboot the router. In case it is unhappy and refusing to connect for any reason.

[Workingman]

Thanks Suff. A router reboot had already been done. When we went off board it became apparent that the DNS server error was a red herring and throwing us off track. We were going to do all the ipconfig bits and pieces but checking the adaptor in Dev Man threw up a problem. Uninstalling and letting W10 reinstall after a reboot did not solve it - the damned thing is flip-flopping and reinstalling and then updating drivers does not change things.

[Suff]

Hard remove the driver with the option to delete the driver from the INF section checked?

If it was working and is now flip flopping, it sounds like a hardware issue.

I'm assuming this is a wifi issue? Tried a USB wifi adapter?

The other option, PC wise, that I use for testing, is a USB3.0 Gig ethernet adapter to get out of the driver loop and move away from the onboard hardware.

Have you looked in the Windows Event log for error codes? I had a Bluetooth issue with my Work laptop. The day after it arrived, I found out later, in the event log, it started throwing errors in the log. It got worse and worse until I lost bluetooth completely. When I went to the logs and saw what happened, I shut it down, took the back off, waggled the Wifi/Bluetooth card and tightened it back up again. Problem solved, no more issue.

In-between I was using a USB Bluetooth adapter and that worked fine.

The onboard adapter driver would install, say it had installed correctly and up to 30 seconds later it would throw an error code and go amber in the device manager. Looking in the event log proved that immediately before the device manager error, it threw two errors in the event log.

Worth checking out.