Potential DNS Issue on Windows 10

[Nelson_9]

Hi all,

When I turned on my pc after class today, I found myself being unable to access websites such as twitter, or ign.
Noticed my home Ethernet connection was some how set to public, and that led me to believe it was a firewall issue. Disabled my firewall, set it back to private. This didn't seem to fix anything and actually made it worse.

Some websites, like reddit still works for the most part and so does amazon when I use 176.32.98.166. I can even use Skype and call a friend and talk with no issue
So this led me to believe its a DNS error, so I went out and ran a few commands I found online in the command window. Nothing has seemed to change. Also factory reset my modem/router.
When using chrome I received the error DNS_PROBE_FINISHED_NXDOMAIN.
And ERROR_NAME_NOT_RESOLVED
When using edge, no error
Internet explorer gave an error saying "network protocols are missing" or something in that nature. I'm currently stumped. I tried repairing my Ethernet drivers, PC has a gigabyte mb that uses killed networking, if that helps.

Also tried setting my DNS to 8.8.8.8 and 8.8.4.4 but nothings worked.

Any assistance would be greatly appreciated.

 

[Ralston18]

Were you able to see determine what "network protocols are missing".

Did you run the networking troubleshooters to see if they are able to identify and fix the problem ?

(If the troubleshooter does not fix the error you may be able to find out more about the error via "details".

 

[Nelson_9]

When I hover over the network diagnostics, it says "Windows Sockets registry entries required for network connectivity are missing"

 

[Nelson_9]

Sorry, not good at using this on mobile. But like I said on another post, I got message relating to sockets. When I tried repairing as administrator, windows network diagnostics was unable to fix the issue

Were you able to see determine what "network protocols are missing".

Did you run the networking troubleshooters to see if they are able to identify and fix the problem ?

(If the troubleshooter does not fix the error you may be able to find out more about the error via "details".

 

[Nelson_9]

From browsing the web with the same error message I posted I found a Microsoft post from a few days ago with others having a similiat issue. Which appears to be caused by a recent update. Apparently the Winsocket Registry might have been corrupted or something like tha . I'm kind of afraid to go ahead with their suggested fix because it involves deleting the registries, and because I'm not 100% sure that will fix my problem,big you have a comment on this I'd, love to hear your input

Were you able to see determine what "network protocols are missing".

Did you run the networking troubleshooters to see if they are able to identify and fix the problem ?

(If the troubleshooter does not fix the error you may be able to find out more about the error via "details".

 

[Ralston18]

Yes: I know about that......

I have two of three systems down with that same problem and none of the fixes I have found have worked... The two systems that are down are wired. Wireless system is working for the moment. All Windows 10 systems.

Google the "Windows Sockets Registry......" phrase and you will find many other similar situations.

Some solutions have worked for some people but not for others. Or different solutions may work.

Could be related to a Windows 10 update.

Anyway "google" it and do some reading. See what solutions, if any, seem to fit into your situation. Do not rush to try any given one until you are comfortable with what it requires and what it does. And the risks involved - some registry changes could be necessary.

At least you can get a start on it all.

I am really hoping that another forum member will jump in with a new possible fix.

 

[computertech82]

could try resetting it in dos (admin) netsh int ip reset then enter, then restart computer. If still not working, you might want to get a computer tech to take a look.

 

[Nelson_9]

Might have jumped the gun here buy I deleted the winsock 1 and 2 keys as per this Microsoft post. I made a backup of my entire registry and then deleted them. Went to reset TCP/IP via the disk method they said and I get an error saying" this program is blocked by group policy . Tried to remerge the backup registry and I get an error when trying to do that as well...Beginning to panic . When I tried to do a reset of winsocket it said the files no longer exist, so my backup didn't work... Really feel like I might've shot myself in the foot here.

I can still roll back to windows 7... Would that be a viable solution or wod driver conflicts screw that all up? I don't have a reset disk for my PC unfortunately so I couldn't reinstall windows. Would a restore point br viable ?

Yes: I know about that......

I have two of three systems down with that same problem and none of the fixes I have found have worked... The two systems that are down are wired. Wireless system is working for the moment. All Windows 10 systems.

Google the "Windows Sockets Registry......" phrase and you will find many other similar situations.

Some solutions have worked for some people but not for others. Or different solutions may work.

Could be related to a Windows 10 update.

Anyway "google" it and do some reading. See what solutions, if any, seem to fit into your situation. Do not rush to try any given one until you are comfortable with what it requires and what it does. And the risks involved - some registry changes could be necessary.

At least you can get a start on it all.

I am really hoping that another forum member will jump in with a new possible fix.

could try resetting it in dos (admin) netsh int ip reset then enter, then restart computer. If still not working, you might want to get a computer tech to take a look.

 

[Ralston18]

Yes I have seen the registry winsock key method but the group policy block has popped up for some folks.

Computertech82's suggestion did not work for me. It seems to have worked in some cases and I remember seeing a script with a series of netsh commands including that one. Have tried those as individual commands just to keep an eye on what happens.

You could go back to Windows 7 but eventually would end up with Windows 10 again and the problem could re-appear.

At least get your data backed up and proven to be recoverable.

 

[Ralston18]

Just posting an update for anyone interested. Have been working through the problem on and off over the last few days.

My Event Viewer logs are full of 7001 errors.

Browser service depends on workstation service which failed to start due to a dependency group.

To make a long story short I have been working through the various services and dependencies to identify the culprit. Have started, stopped, and worked through a variety of services using services.msc

LANMan Workstation pops up a few times having failed due to mrxsmb20 not starting.

SMB20 mini redirector seems to come up which involves the mrxsmb20 service (name).

I have attempted a couple of fixes involving .bat downloads from MS and registry entries.

Next on the "fix list" is to restore mrxsmb20 from my Windows 10 CD. However, I keep getting hints that the real problem is due to a previous MS update (1511 maybe). Did note one reference to a possible MS fix this coming March......

Will be happy to hear any other ideas, leads, or fix suggestions. Thanks.