Windows 10 / SMB - Network Drive Connection Error 0x80004005: Unsuccessful Troubleshooting Attempts

Hello,
I have a problem with mapping or connecting to a resource in the lan network. Throws error 0x80004005 when trying to map a running resource on the server.

- A tip of unchecking SMB1 components of the windws system and checking it again doesn't help, after each restart of course.
- Resetting the whole network doesn't help, troubleshooter, you know the same thing
- other computers can access these resources without any problems
- system clean without any viruses, trojans, etc.
- after mapping in DOS, a bit different error, error No. 6

PS
I already have this problem on 2 computers with windows 10 in 2 different networks and the computers are also completely different, the folder and HP, they only connect with Windows 10! I fought on pc1 for half a year and I could not do it, this problem arose with the other client and I am also lying despite many hours of struggle. Is there any spec that knows the problem ?!

This problem appeared some time after the system was installed, has it existed from the very beginning? I had a similar case after Win10 Updates were automatically installed. And what's most interesting, just like you, this problem did not occur on all computers, only on a few. Despite the fact that all computers got the same system update.

There was no problem before, it connected without problems. on the second pc he also used to connect about 4 months ago. Possible update, if so, the question is which kb hotfix should be removed? Interestingly, I noticed that the NAS server, which also has a website, does not even display the NASA website from this "damaged" windows, throws ERROR CONNECTION REFUSED in chrome. But it responds to ping and ssh connects fine too.

The second computer has the same error when connecting to the network resource, but not to the NAS but to the password folder shared on the host with windows 7 by prof. Also, probably there is nothing like a blacklist in the resources of these machines that they provide (one is NAS on Linux - Rockstor and the other is win7) so the problem is 99% on the side of these updated windows 10. But what exactly hurts them?
Help!

It may not be easy to identify a specific package. From what I remember, the problematic was: Windows 10 Update 1709, after which Microsoft described ways to restore SMB operation. Uninstall and check, maybe it's this one.

PS. You wrote about deselecting / selecting SMB1 in system components, did you check if SMB2 is enabled in "broken" Windows? The easiest way is via PowerShell> Get-SmbServerConfiguration | Select EnableSMB2Protocol

Yes, I checked the result below. So it's on. And the error is still as it was, so it is.

You have described here:
https://support.microsoft.com/en-pl/help/2696...-disable-smbv1-smbv2-and-smbv3-in-windows-and
Using SMB1 is insecure, can't you disable SMB1 on NAS or file server and use higher versions?

But balls, actually after turning off the SMB 1.0 server on the server, so I set the support from 2.0 to 3.0 and now it flashes! Thank you very much! It's a pity that microosft could not write this in the message only 0x80004005 which means many different reasons. Microsoft's products are getting worse and worse ... It's important that I succeeded, I fought it for a few months!

And do you know how you can make this win10 workstation still support SMB 1.0?

You have to disable SMB2 / 3 eg with Powershell commands. But it is not recommended. There are limitations to disabling these services.

I checked the status of smb1 on win10, it's supposed to be on, but I can't connect to the resource from win7, the same error

So the question is how to disable in win7 smb 1.0 if there are no such options in "add remove windows features"? nor is there powershell in this system (win7 prof sp1)?

There is only a need to install. In the link provided earlier you have how to disable SMB1.0 in W7 using the registry:

To enable or disable SMBv1 on the SMB server, configure the following registry key:
Registry subkey: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ LanmanServer \ Parameters
Registry entry: SMB1
REG_DWORD: 0 = Disabled
REG_DWORD: 1 = Enabled
Default value: 1 = Enabled (no registry key is created)

To enable or disable SMBv2 on the SMB server, configure the following registry key:
Registry subkey: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ lanmanserver \ parameters
Registry entry: SMB2
REG_DWORD: 0 = Disabled
REG_DWORD: 1 = Enabled
Default value: 1 = Enabled (no registry key is created)


Note You must restart your computer after making these changes.

To be sure, I will still ask if these options are meant to add a key ("folder")?

Add a 32 DWORD value named SMB1 and a value of 0 and an SMB2 value of 1. Then you will have SMB1.0 disabled and SMB2.0 enabled.

check mapping by name ...
Microsoft has fixed it in version 1809 and if you have to enable this feature manually or in the answer file, then the name of whether IP is working properly is already.

I switched to SMB2 and everything flashes. Thanks a lot again

in win 10 smb1 is disabled by default because they no longer support, it helped me to enable smb1 from the link above

zibq wrote:

https://support.microsoft.com/pl-pl/help/2696...-disable-smbv1-smbv2-and-smbv3-in-windows-and