Share via

Unable to view and access shares on Synology Diskstation after update 1511 (10586.104)

Question

Monday, March 7, 2016 3:24 PM | 1 vote

Hi,

I am unable to view my shares on my diskstation after my desktop was updated to update 1511.  I can still view/attach and use the shares as normal using my laptop which is running version 10547.

I've been in touch with Synology tech support, who tried to help but in the end said it must be a Windows issue.

When I try to connect to the diskstation using start/run "\diskstation" I just get the following errors, the "Just a moment" error hanging.

I do not have Windows credentials in credentials manager either.

Any help much appreciated.

Thanks

All replies (17)

Monday, March 7, 2016 7:38 PM | 1 vote

Well 10586.122 is the latest update, so check updates and try installing that see it that helps. It includes and has been reported by used to fix the issues people saw with 1511 before that update was released involving seeing NAS shares etc.

The error states invalid address, if you ping diskstation does that resolve to the expected \ correct address?

Tuesday, March 8, 2016 10:32 AM | 1 vote

Hi,

I am running version 10586.122, this issue seemed to start from version .104.  I can access the Diskstation's web admin portal using a browser using http://diskstation:5000 just fine.  From there I can see it's IP address is x.x.1.74, when I ping diskstation its resolving to the same IP address.

When I try "\diskstation" I just get a white File Explorer window and those two dialogue boxes overlaid.

Tuesday, March 8, 2016 3:11 PM

Hi,

This problem results when an administrator, the owner of the file or folder, or a user with the Change Permissions permission for a file or Full Control permission for a folder, changes the access control list (ACL) on the file or folder. Some of the changes that could deny a user access to a file or folder they should be able to access include:

1. The user or group was unintentionally removed from Group or User names on the file's or folder's Security tab.

2. An explicit Deny has mistakenly been applied to the user or group.

3. A conflict between share permissions and NTFS permissions was created when someone changes permissions without examining both types of permissions.

Please check the shared permission and the folder security permission to fix this issue:

  • Click on the "Security" Tab of the Folder you want to share.
  • Then "Edit..."
  • In the new window click "Add..."
  • In the new window click "Advanced..."
  • In the new window click "Find Now..."
  • Select the user who needs the permission to acces the folder.
  • Go back to the "Permissions for " dialog.
  • Choose the user you added.
  • Set permission to "Allow" / Full controll (Or at least read permission)
  • Click Apply.

On the sharing tab, the only entry you Need is:

  • Everyone
  • With permission "Full Controll".

You can manage the permissions with the NTFS-Permissions of the Security Tab.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Tuesday, March 8, 2016 7:01 PM

Looking at posts on the Synology forum seems this one is affecting different update versions in different ways, with no one definitive fix.

https://forum.synology.com/enu/viewtopic.php?f=49&t=106924

Is on going since the start of the November update. The second post would be worth a try I would say;

" (From an admin Command Prompt);

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

And reboot fixes it...
Please note it should be used as temporary fix and should be reverted as soon there is more proper solution."

Not the exact same issue as you but would be interesting to put Windows 10 on SMB1 and see if it works.

Wednesday, March 9, 2016 8:44 AM

Thanks Mr Happy, I tried that, no effect with the issue I am having.

Wednesday, March 9, 2016 9:01 AM

Hi Kate,

The Synology NAS drive does not use Windows, I think it's linux.  However its not running with "Windows ACL" setting for the shares as the volume I have configured on it does not support this.

Maybe there was a change in 1511 to enforce a windows ACL share?  The reason I say this is I can still access the shares just fine with the evaluation copy of Windows 10 on my laptop.

Wednesday, March 9, 2016 7:43 PM

Well turn bath on SMB2\3

sc.exe config mrxsmb20 start= enabled

and reboot.

Did you get any Windows Updates yesterday? Don't suppose the 'magically' fixed it? The reason  I ask as in the thread I posted a link too different uses seem to get this issue with different updates and an update fixes for some users but not others.

If still no good perhaps try a clean up of the network interface and config. Take a system restore image before doing this as I have heard of one user running into issue after doing this. Again from an admin command prompt;

netcfg -d

Performs a cleanup on all networking devices.
This will require a reboot.

Wednesday, March 9, 2016 9:44 PM

I got the Windows update today, now running ver .164)  Although my orange shutdown/log off/ startup screen has returned :(

I turned SMB 2 back on for the Diskstation (tick box for that and MTU), it was on, but I turned it off as Synology Tech support said Large MTU maybe be causing issues if not setup properly on my network.

sc.exe config mrxsmb20 start= enabled does not work I get  "Error: Invalid start= field"

The issue in the Synology thread you posted seems subtlety different to what I am seeing, I can see the Synology Diskstation under "NETWORK" and .....  oh hang on I can now see the shares.   But only if I do the following.

1. Double click "This PC" from the desktop

2. Under "Network Locations", double click on DiskStation (it has a blue Synology logo)

3. Browse and access content for all shares.

If I try \Diskstation, save error as before

If I open Windows Explorer, under Network I see DISKSTATION with a generic blue monitor logo, if I click on DISKSTATION, same error.

So I can access the shares but only from "This PC" method...   Almost there... :-)

Wednesday, March 9, 2016 10:20 PM

Sorry type in my post from How to enable and disable SMBv1, SMBv2, and SMBv3

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

Interesting the Synology NAS shows under Network locations. Normally would think that is for mapped drives and such, do you have any Synology software \ utilities installed on the PC?

When connected via that method from a admin powershell prompt, what does;

Get-SmbConnection

show?

Thursday, March 10, 2016 9:26 AM

I have no Synology software installed on the PC.  The NAS drive I have is running software that only supports up to SMB2, not sure if this matters or not.

Will check the Get-SmbConnection when I get home.

Thanks for your help so far

Thursday, March 10, 2016 6:34 PM

Hi,

Get-SmbConnection returns nothing

Thursday, March 10, 2016 9:32 PM

Interesting, and that is with a connection open? Is that a File Explorer windows that opens (or continues) when the Synology icon is click in Network locations?

If you on a command prompt do;

netstat -n | findstr "x.x.x.74"

(replacing the x's with you Diskstation address, you x'd them out above, standard Diskstation that is a private class address)

What does the port, the number after the : on the Diskstation IP show?

tbh not sure this will help just interesting that connects so trying to work out how.

Friday, March 11, 2016 7:17 AM

"This PC" looks like this, its the "This_PC" part of of File Explorer.

Netstat returns the following

TCP 192.168.1.67:62911 192.168.1.74:5000 TIME_WAIT
TCP 192.168.1.67:62912 192.168.1.74:5000 TIME_WAIT

Friday, March 11, 2016 6:57 PM

Well port 5000 used by What network ports are used by Synology services? in serval places, but guess this is File Station or Download Station in this case if you can see the files that way. Anyways not CIF \ SMB.

Running out of ideas here, see if the Trouble Shooting (search start for trouble) Network and Internet > Shared Folders, and then Network Adapter have any insights.

Saturday, March 12, 2016 9:11 AM

I tried to "Troubleshoot" Shared folder access and the error is "Your user account doesn't have permission to access the share"

If I connect to the diskstation from the laptop and run get-smbconnection I see a line lists the credentials and dialect as 1.5

If then enable SMB2 and MTU on the diskstation, and run get-smbconnection again I see dialect is now at 2.1 on the laptop.

I get the same error as shown in my my first post, when I try and connect to my Windows 10 laptop as well.

Friday, March 18, 2016 5:47 AM

Hi，

Have you tried to reset the permission on shared folder on your NAS?

Refer to this link:

https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/file_share_privilege

https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/How_to_manage_Windows_ACL_permissions_from_Windows

Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

Since the latest updates for 1511 has released with many fixes, please install them all to lead your Windows 10 to 10586.164, then check if the issue still persists.

I recommend you also contact Synology support to see if there is any known issue on their side.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Friday, March 18, 2016 8:56 AM

HI,

Thanks for your reply.   I am running the latest version of Windows 10 on my desktop (as you can see from my post on March 9th when my desktop was updated to version .164)

I also cannot access my laptop from my desktop, same error occurs as to when I try and connect to the NAS drive.

I can access the NAS from my laptop just fine as I stated in my latest post, so I can only assume there is a problem with the latest version of Windows 10 that has still not been fixed in build .164

I've contacted Synology support and they said it's a problem with Windows 10, as I can still access the drive from my laptop.

Steve