Time goes on and so do update all the systems we use – as much as any does Windows 10 and not so much – D-Link DNS-323 network storage disk system. This has caused, after a major Windows 10 update, the network share previously available on the D-Link nas, to become not available to access from the Windows 10 machine. More specifically, the big red error message above is popped.
“You can’t connect to the file share because it’s not secure. This share requires the obsolete SMB1 protocol which is unsafe…” etc etc. A long message, ultimately asking you to update the share to use SMB2.
Well let’s turn on SMB2
Well, I tried, but there is no option to enable SMB2 on the DNS-323.
So what’s the story?
A bit of searching and turns out Microsoft has already back in 2016 urged everyone to stop using SMB1 and finally shut it off from use now. Microsoft has also listed all known products that use SMB1 and D-Link DNS series NAS-s are listed.
In the D-Link support section the situation is explained as follows: The latest update from Windows 10 disabled SMB v1.0. The D-Link DNS line of NAS devices uses SMB v1.0 and does not support SMB 2.x. You must enable SMB 1.0 in Windows 10 to map a drive and view drive content. So no software update from D-Link, just reverting back to SMB1. And they also suggest you turn on all SMB1 services on your PC to solve it.
Why would I need to enable SMB1 server on a Windows 10 machine if you only need to connect, not serve files? You are right, you don’t, so don’t follow those instructions.
Here is how you gain back access to your D-Link DNS-323 network bay from Windows 10:
- Type “Turn windows features on or off” to your Windows 10 search box and open it
- Scroll down till you find SMB 1.0/CIFS File Sharing Support. Click on the plus sign to expand it and mark only SMB 1.0/CIFS Client. Click OK.
Now you should be able to connect and access your D-Link DNS-323 NAS without any issues. But bear in mind, it is not safe to use SMB1 – two global ransomware outbreaks, WannaCry and Petya, spread quickly because of a vulnerability in Server Message Block version 1.