Windows 10: missing network protocols prevent access to shared folder

From one of my Windows 10 machines I am unable to access the shared folders on the other. The troubleshooter says "One or more network protocols are missing on this computer" and "Windows Sockets registry entries required for network connectivity are missing." Does anyone have any ideas?

I have run sfc /scannow, but no problems were found. I don't get the problem when sharing in the other direction or when accessing the shared folders on the same machine.

This comes amidst a cluster of sharing-related problems. Before the reboot after which the present problem manifested itself, shares going in the other direction were invisible in the network browser (but could be accessed via the search bar). Also, the machine in question does not appear in the HomeGroup browser even though it is a member of the HomeGroup.

:)

 

One or more internet protocol missing

Hi!

When do you get this error? Are you wired or wireless?

I got this error setting up a Local Network. My advanced sharing options where not the same on the different machines. When trying to access a share on the network, or limiting the folders shared on a machine. Then when I enabled HomeGroup. (The HomeGroup
required network discovery enabled for public network. Even if my connection was in Private Network.)

The missing protocol was not always on the machine the network diagnostics tool was ran on.

 

4/2/2016 windows 10.0.10586 File Explorer will not connect to MyBookLiveDuo

The last successful connection was on 3/28/2016. The conclusion is that a Windows 10 update has caused the problem.
File Explorer does show device MyBookLiveDuo

Expanding responds with Windows cannot access \\MYBOOKLIVEDUO

Details: Error 0x80070043 The network name cannot be found
[Diagnose] responds with 'one or more network protocols are missing on this computer'

Try these repairs as administrator: responds with 'one or more network protocols are missing on this computer' Not Fixed
Explore Additional Options - Find Related Troubleshooters - Incoming Connections - Share File or Folders

responds with 'one or more network protocols are missing on this computer'

Try these repairs as administrator: responds with 'one or more network protocols are missing on this computer' Fixed
No Change:

File Explorer does show device MyBookLiveDuo

Expanding responds with Windows cannot access \\MYBOOKLIVEDUO

Details: Error 0x80070043 The network name cannot be found
Using File Explorer to connect by IP address \\192.168.x.x results in the same problem.
Using File Explorer to connect to a file path \\mybookliveduo\sharename

Windows Security Connect to mybookliveduo prompts for a user name and password

Entering the proper credentials responds with \\mybookliveduo\sharename is not accessible.
Network and Sharing Center - Change advanced sharing settings

using either Allow Windows to manage homegroup connections or Use user accounts and passwords to connect to other computers has no effect on the problem.
Turning the Windows Firewall off has not effect on the problem.
http://mybookliveduo/UI/# allows me to login and all diagnostics passed

The Windows 10 WD App and Windows Media Player is able to connect to the public folder and play media files

The Windows 10 WD Discovery App does show MyBookLiveDuo but does not allow Browse Network Shares or Map Network Shares.
Turn Windows Features on or off shows SMB 1.0 CIFS File Sharing Support is enabled.
Searching for historical fixes to the problem has been unsuccessful. Any help is greatly appreciated.

 

Over discussed issue, due to Microsoft in their infinite wisdom thought that networking would be more secure by crippling it, instead of fixing their mistakes. Some have been able to disable SMB 2 & 3 and get it to work again.

 

Thanks for your suggestion. Strangely though, the problem seems to have corrected itself (without even a reboot, although I had rebooted several times previously in my attempts to solve it). But I will try your suggestion if I continue to have further weird SMB problems in the future.

 

Also, See this thread: One or more network protocols are missing, solution