Can't connect to SMB share "Windows cannot access"

Askejm ​ 1 Reputation point
2022-04-17T20:06:07.573+00:00

I use my NAS for backups (truenas), with an SMB share. I reset my PC recently and added it like normal. Worked fine. However, after a day it stopped working and I was unable to connect to it. Now when I try to connect to it I get this:
193696-image.png
It works fine on my laptop
193687-image.png
^ Before the error box appears (after loading for quite a while)
193660-image.png
I tried:

  • Redoing the ACL perms
  • Adding network location
  • Typing IP address in the file path
  • Tested: "\192.168.244.3", "\192.168.244.3\MainBackup", "\192.168.244.3\MainBackup\MainBackup"

I was told to post this here

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,361 questions
Windows Server Backup
Windows Server Backup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Backup: A duplicate copy of a program, a disk, or data, made either for archiving purposes or for safeguarding valuable files from loss should the active copy be damaged or destroyed.
476 questions
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Dan Jackiels 11 Reputation points
    2022-08-23T12:09:07.52+00:00

    Hey,

    I was having this same issue but I managed to solve it. This is what worked for me: https://kb.synology.com/en-ro/DSM/tutorial/Why_cant_access_shared_folder#x_anchor_id15

    234112-2.png

    In short:
    Search for Credentials Manager in Windows
    Select Windows Credentials
    Under "Windows Credentials:"
    Delete every entry related to your NAS
    After that you should be able to connect to your NAS without even restarting anything

    Hope this helps!

    2 people found this answer helpful.

  2. Vasily Sosnovsky 5 Reputation points
    2023-05-06T10:27:55.7466667+00:00

    For me this steps were helpful:
    1. Click on the Start menu

    2. Type cmd to find the command prompt

    3. Right click on "Command Prompt"

    4. Select "Run as administrator"

    5. Type the following command : DISM /Online /Enable-Feature /All /FeatureName:SMB1Protocol

    6. Confirm

    1 person found this answer helpful.

  3. MotoX80 34,346 Reputation points
    2022-04-18T12:41:31.257+00:00

    Does your Truenas device have the equivalent of the System/Security/Application event logs? What error do you see on the NAS?

    SMB1 would be the most likely suspect. I found this on the Truenas site.

    https://www.truenas.com/community/resources/how-to-kill-off-smb1-netbios-wins-and-still-have-windows-network-neighbourhood-better-than-ever.106/


  4. Askejm ​ 1 Reputation point
    2022-04-28T08:21:07.837+00:00

    Sorry for the delayed response
    197262-msdt-ydjfpbhpsg.png
    197303-powershell-4ka1tp8slt.png
    Last one was loading for ages
    197305-image.png


  5. Aaron You 16 Reputation points
    2022-08-05T08:56:55.987+00:00

    Hi. I am facing the exact problem with TrueNAS as well, with the difference being that I am on Windows 11 21H2. After swimming through unuseful posts for hours, I felt the need to start actively seeking help.

    I have a few more clients with different OSes to try out. Seems like to me that only my Windows client is unable to connect to this share. All my other devices: Mac, iOS built-in SMB client, and 3rd party apps on iOS and Android are able to connect to the share.

    I am sure the SMB server supports SMBv2 and v3, with v1 being disabled. Same on my windows machine(client side) as well. I have yet to try enabling SMBv1 support on these machines for the same reason why the protocol is depreciating.

    Let me know if more information is needed.

    Thanks in advance.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.