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

Askejm 1

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:

It works fine on my laptop

^ Before the error box appears (after loading for quite a while)

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

6 answers

Dan Jackiels 6 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

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!
Please sign in to rate this answer.

1 person found this answer helpful.
Robert Coombes 1 Reputation point

2022-08-23T16:29:11.653+00:00

Tried these already and it does not work. Even tried adding the correct information without success either.

Luca Avalle 6 Reputation points

2022-09-12T20:43:38.353+00:00

Excellent! sorted me out in seconds

Natalia Haze 0 Reputation points

2023-02-14T04:00:06.8533333+00:00

They need to code it into Windows to do this automatically. I think something to refresh that would be beneficial. Maybe something under the user and password dialogue boxes in small n font like: "having trouble? Click here to reset your Samba connection. ". That easy. Please fix Microsoft.
Sign in to comment
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
Please sign in to rate this answer.

1 person found this answer helpful.
Alexandre 0 Reputation points

2023-06-23T23:36:03.3833333+00:00

Thank you so much! Your answer was the only one that helped me.
Can you give a description of the command you specified in your answer? What exactly does this command do?

Pascalino 0 Reputation points

2024-01-12T02:07:28.17+00:00

Enabling SMBv1 is generally discouraged due to security concerns. SMBv1 is an older version of the SMB protocol and has known security vulnerabilities, including the infamous WannaCry ransomware exploit. Microsoft recommends using newer versions of the SMB protocol (SMBv2 or SMBv3) for better security.
Sign in to comment
MotoX80 31,976 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/
Please sign in to rate this answer.
Askejm 1 Reputation point

2022-04-20T17:18:56.36+00:00

I'm not the smartest with truenas so I don't really know. And that long post you sent, do you want me to run the last part with the registry edits?

Askejm 1 Reputation point

2022-04-20T19:27:43.16+00:00

I tried disabling it with that regedit, and it didn't do anything. Also, I noticed I don't have SMB 2

I also tried checking Wireshark filtered by ports 445 and 139. Nothing popped up

MotoX80 31,976 Reputation points

2022-04-20T20:03:59.027+00:00

Let's do a few tests first. Here is good site that I found.

https://helpdeskgeek.com/windows-10/fix-cannot-access-or-see-shared-folder-from-a-windows-10-pc/

Verify that you have applied all available Windows Updates, and that your WIFI network connection is set to private.

That site has instructions to set your PC up for sharing to other computers. You can skip over that part and scroll down to the "Use the Shared Folders Troubleshooter". The troubleshooter will prompt you for the share name. Enter \192.168.244.3\MainBackup and let it run.

See if that detects anything.

If that doesn't fix it, open a Powershell prompt and run these commands.

Test-NetConnection -ComputerName 192.168.244.3 -CommonTCPPort SMB net view \\192.168.244.3

What do those commands show you?
Sign in to comment
Askejm 1 Reputation point

2022-04-28T08:21:07.837+00:00

Sorry for the delayed response

Last one was loading for ages
Please sign in to rate this answer.
MotoX80 31,976 Reputation points

2022-04-28T12:05:47.843+00:00

I don't know. Kinda guessing at this point.

Reboot the NAS, and on Windows temporarily disable the firewall for all 3 network profiles.

https://support.microsoft.com/en-us/windows/turn-microsoft-defender-firewall-on-or-off-ec0844f7-aebd-0583-67fe-601ecf5d774f

Does the NAS have an HTTP interface? Does that work ok? What logging capabilities does it have? Any errors in there?

Gary Nebbett 5,721 Reputation points

2022-04-28T12:28:41.307+00:00

Hello Both,

You could try looking at this page: https://gary-nebbett.blogspot.com/2021/06/mapped-network-drive-reconnection.html. The symptoms look consistent with the NAS always expecting a "multi-protocol negotiation". The referenced page describes the problem in detail and suggests a workaround.

Gary

MotoX80 31,976 Reputation points

2022-04-28T12:30:19.627+00:00

Thanks Gary.
Sign in to comment
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.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment