5

Hope you're well.

Detail Issue: I'm accessing my network files hosted on a Synology via windows explorer (unc path &/or mapped drive) and since a few days I'm unable to open any file via explorer or any application; I'm getting the following messages:
Open a picture: "it looks like you don't have permission to view this file. Check the permissions and try again.
Open any other file : "The directory name is invalid."
Open with other program than Windows one also mention permission issue.

Tentatives Issue: Diskcleanup, SFC /Scannow (clean), chkdsk /f /r (clean), Delete all network drives & windows credential for this network, killing all tasks, safe boot, disabling WinDefender, Firewall, checking if new ethernet drivers, ccleaner...

Background Issue1: I'm using b16251 of W10x64 and had this problem twice with older versions of W10. Only solution I found at the time was to format and reinstall windows as I'm completely handicaped in this situation.
Please note I can access properly all files of that network from other computers using W10 & W7 so it's definitely linked to this setup. Not sure if it's related to insider preview as I had this problem on Creator Update 1703 and upgraded to preview thinking it will solve the problem...

Can you please help me trace and fix this issue please ? Thanks a lot!

fluxtendu
  • 7,219
seiferflo
  • 51

5 Answers5

2

Some solutions that work with some NAS are :

  • Access the NAS by its IP address rather than by name, as sometimes the name is badly published.
  • Enable SMB 1.0, as this old protocol is well-defined, if your computer uses a more advanced SMB protocol than is supported by the NAS. In Windows this is done in
    Control Panel > Programs & Features > Turn Windows features on or off.
harrymc
  • 498,455
1

Make sure the clock on both client and NAS are synced up. If either one is off by too much you might see issues like this.

Does the NAS allow connecting using other protocols than SMB? you might be able to use to connect.

Cpt.Whale
  • 10,914
1

I encountered this issue with Win10 laptop connecting to Synology DS416 and it seems that issue is caused by SMB3 which allows transport encryption.**

Temporary solution is log into Synology system, then go to Control Panel -> File Services -> SMB -> Advanced Settings and click Clear SMB cache button which is last item in that window.

Permanent solution seems to be: (again in Synology -> Control Panel -> File Services -> SMB -> Advanced Settings)

  • EITHER set Transport encryption mode to Disable
  • OR set Maximum SMB protocol to SMB2 (which does not support encryption) *

Make sure your Synology system is updated. Older versions seem to have different "advanced settings" screen.

Also I strongly advice against enabling SMB1 which was suggested in previous answer. SMB1 has significant security holes which will never be fixed and should be avoided unless your computer is running WinXP (which supports only SMB1)

*EDIT 2018-01-12: permanent solution is not permanent as the error occured again today on one of our computers.

**EDIT 2018-01-30: After several weeks, Issue happened again despite SMB3 and encryption being turned off. That suggest that issue has nothing to do with SMB3 neither Transport Encryption mode.

EDIT 2018-08-15: During last week, two more of our computers started encountering this error on regular basis.

I will post update if I figure out something.

Pavel Cernik
  • 11
0

Workaround: Same problem here, in my case, disconnecting the lan cable (it switches automatically to wifi) and reconnect the lan cable solves it for the moment.

(win10 and Synology nas.)

mcvries
  • 11
0

A solution that seems to work on these Systems ...
Synology DS211 /w DSM 6.1.3-15152 Update 8.
Win10 Pro Workstation, Version 1709, Build 16299.192

Issue accessing shared files on Synology via both UNC and Drive letter.
Error message: "The Directory name is invalid ..." when double clicking a file to open.
Rightclick a file and select "Open with ..." circumvents the error.
MS Office programs (word, excel) fails to save files to shared location, same error message.

Solution:
On DSM changed FileServices - SMB Advanced Settings to following:
Maximum SMB Protocol: SMB3
Minimum SMB Protocol: SMB2
Transport encryption mode: Auto

Status:
All is well for the time being :o

Carsten Eickhardt
  • 1