Printable View
I've just put together a new PC running Windows 10, and I'm trying to get file access to my Synology NAS using File Explorer. I'm running the 'private' network profile, and I've got network discovery switched on. Unfortunately I just can't seem to get file access working. It's working fine on my old PC; I can see the Synology NAS under 'network' on file explorer, & I just login with my password to get file access. But on the new PC, the NAS isn't listed. Can anyone help? Thanks!
Get that all the time.
Each W10 update seems to break it. Try connecting to it using Synology assistant and making sure DSM and all drivers are up to date.
Failing that - turn it off and turn it off again :)
This is a problem with Windows clients and non-Windows servers running Samba, with current Window 10 builds, Microsoft is disabling SMB1 client support due to legitimate security concerns, which means NetBIOS network discovery no longer works, so Samba servers wont show up.
You have two options to work around it, the first is to either reinstall the SMB1 client component on your Windows machines, as well as uninstall the autoremover for that component. The other option is much more technical, you'd have to download, compile (with the right architecture for your NAS), and run wsdd2 on the NAS, it'll require shell access to your NAS and and you'll need to fit it in with DSM's process initialisation system. Ideally Synology should already be bundling wsdd2 into DSM (or better yet, upstream Samba should be bundling it with the server software), but that doesn't seem to be the case as of yet.
Turns out they might have, but just haven't enabled it by default for some reason:Quote:
Originally Posted by aidanjt
https://www.reddit.com/r/DataHoarder...up_on/e3get8t/
Let me know how you get on.Quote:
The latest Synology software now supports WS-Discovery natively. I enabled it and, bang, it appears in the Network Neighborhood now. It's in Control Panel, File Services, Advanced, "WS-Discovery" option at the bottom.
Thank you so much for all your help - I got there in the end, after a lot of faffing around. Big thanks to Aidanjt especially, that Reddit post was the key to getting it working. Firstly, I'd forgotten that I'd changed the default workgroup name, which was one reason why I couldn't connect. Next, turning on WS-Discovery allowed me to see the Diskstation in network neighbourhood, but I couldn't actually connect to it. Finally through trial & error, I found that in SMB > Advanced settings, I had to enable 'Maximum Protocol' to SMB3, in order to get file access. Why on earth Synology don't enable these settings by default is beyond me! Anyway, thanks again for all your help!
It might be worth setting the minimum SMB protocol to version 2 as well. I'm fairly sure Samba is not at risk to SMBv1 worms, but since every Windows release since Vista supports at least v2, why take the risk?
Thanks for the tip, I'm very grateful for your help - it's quite a relief to get it sorted out! :)Quote:
Originally Posted by aidanjt