Can't see network shares and computers in win 10

Question

I'm going crazy with this. PC1 is Win 10 Pro, has shares that are seen by other computers on network. This computer doesn't see any shared folder or even computer, but sees media devices, other devices, and network printers and can access to them all these devices.

All other computers on the network see each other, see the nas, see the network printer and see the PC1 shares. The only one with issues is PC1.

When, from PC1, I try to connect to other computer or shares using \\ipaddress, after a few second I get the error "Unspecified Error 0x80004005"

what I have tried so far:

• Disabled firewall on PC1, nothing changed.
• Checked sharing options, everything is fine, network discovery is on, file and printer sharing is on, password protection is off.
• I have checked HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order - Provider Order and HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HWOrder - Provider Order they are both with the correct value of "RDPNP,LanmanWorkstation"
• Checked that "client for windows" is installed on my network adapter
• Ping to ip address works fine, net use to same ip address gives error 67 "network name cannot be found"
• Checked Control Panel -> Administrative Tools -> Local Security Policy Under Security Settings -> Local Policies -> Security Options Set "Microsoft network client: Digitally sign communications (always)" to "Disabled" was already disabled
• Checked that both services are active: Function Discovery Provider Host, Function Discovery Resource Publication
• Tried this, no changes: 1) run cmd as admin 2) sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi 3) sc.exe config mrxsmb20 start= disabled 4) restart

One strange thing: Microsoft Network Adapter Multiplexor protocol is disabled on the adapter. I click to enabled it, when press OK it say "you will disable this service". I reopen the window, the service is disabled.

Anything else I can try to make it work again?

EDIT: I looked to the other possible duplicate question.

• My network is set up as private, as it should be.
• SMB 1.0 is present on my windows component setup
• I get the same error not just with any local ip address, but also with \\localhost and even \\127.0.0.1

System version is Windows 10 Pro Version 1803 Build 17134.112

If I use Filezilla to connect to network nas (that has an ftp server enabled) I can connect succesfully and upload/download files. I can't access it with windows network explorer.

Solution 1

I fixed the issue. Double checking every service I noticed that workstation service was stopped. When starting it, I got the error

"Error 1075: The dependency service does not exist or has been marked for deletion"

Getting into regedit and deleting the relative dependOn key fixed the issue for me.

Solution 2

Open the command prompt as Administrator and run each of the following commands:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Comments

[Run5k]

We are always glad to help, but can you please edit your question to include the appropriate Windows 10 version and OS build number that you are currently using? Thank you!

[Run5k]

Possible duplicate of Windows cannot access \\‌[other computer] error code 0x80004005

[Run5k]

Although the fix action isn't ideal for security reasons, this answer within that Possible duplicate question should alleviate your problem. Here is a good Microsoft article as an additional reference: SMBv1 is not installed by default in Windows 10 version 1709).

[Terix]

@Run5k I've added Win 10 version

[Terix]

@Run5k none of the answers of the other question fix my issue

[Run5k]

That is rather surprising. I would try the following that is mentioned within that Microsoft article: Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them to Automatic (Delayed Start)

[Terix]

@Run5k I already did that, it's bullet point n.7. I tried everything I was able to find on the internet before coming to write a question here

[Run5k]

I am glad to hear that you resolved the problem, but based upon your final solution it sounds like something "broke" within your operating system based upon the extensive modifications that were made during troubleshooting. Without those additional elements in the equation, this is the only time I have ever seen the SMBv1 install not work under similar circumstances.

[Terix]

@Run5k Yeah I noticed that I had a very rare case of malfunction. I hope that my struggle will be of help to other should this issue arise to more people in the future