D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: masterx81 on June 01, 2018, 08:32:24 AM
-
Hi! I own a DNS 320 nas, sharing some documents across the network, with windows worstations.
The share is in r/w for everyone, and the clients access to the nas via the \\ip.address share.
Recently i've installed a new computer. When i open a document from the new computer, eventually the share become inaccessible for the windows 10 computer itself, and also to the other clients. From all the copmuters, if i go to the \\ip.address share i can get the shared folders, but if i try to open the share, it tell me that i not have the rights to open it. When i exit the word document on the windows 10 computer, all seem to start working as before.
I've noticed it with word documents.
I've already tried to disable smb2 on the windows 10 computer, without success.
The firmware is the last on the dlink site.
What i can try to do?
Thanks!
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your DNS? Look at the sticker behind or under the device.
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the DNSs web page under status.
- What region are you located?
What Mfr and model is the main host router?
Windows 10 FAQ: http://forums.dlink.com/index.php?topic=65722.0 (http://forums.dlink.com/index.php?topic=65722.0) and
http://windowanswers.com/windows-rt/windows-10-falls-to-access-network-drives-297748.html (http://windowanswers.com/windows-rt/windows-10-falls-to-access-network-drives-297748.html)
-
You do not have to disable SMB 2, you have to enable SMB1 on your windows 10 machines.
Go to Control Panel > Programs and Features > Turn Windows features on or off. Make sure SMB 1.0/CIFS File Sharing Support is checked.
(http://images.dlink.com/new/articles/A10391/A10391_image7.png)
-
You do not have to disable SMB 2, you have to enable SMB1 on your windows 10 machines.
Go to Control Panel > Programs and Features > Turn Windows features on or off. Make sure SMB 1.0/CIFS File Sharing Support is checked.
(http://images.dlink.com/new/articles/A10391/A10391_image7.png)
I've done both, installed smb1, and deactivated smb2....
-
And is it working now?
You can leave SMBv2.0 enabled...
-
Same issue...
-
So it's not working with SMBv1.0 re-enabled? Did you do a full reboot of your PC after applying the change?
-
Same problem as before. Also done a full reboot :(
-
I looked at my Windows 10 PC yesterday. I can see my DNS-345 and it's a bit older than the 320. I have SMBv1.0 enabled in windows 10. Not sure what the difference could be...
-
Next thing that i'll try is to set a password to the share instead of leaving it open to everyone....
-
Let us know how it goes...
IS there any PC security software installed? you might disable this temporarily and see...
-
Using a password has not fixed, net bet is to disable the av on the workstations....
-
I was reading in the tech press last week that one of the latest win 10 updates has messed up SMB 1 used by most NAS boxes and as yet there isn't a fix for it. It appears to be dependent on network card and drivers - some work and some don't and some people have been able to regain contact with their NAS boxes by back-levelling the network card drivers.
-
I wouldn't put it past MS to not fix that either. ::)
-
There a public link to this article? :o
I was reading in the tech press last week that one of the latest win 10 updates has messed up SMB 1 used by most NAS boxes and as yet there isn't a fix for it. It appears to be dependent on network card and drivers - some work and some don't and some people have been able to regain contact with their NAS boxes by back-levelling the network card drivers.
-
An update to the SMB1 problem but there isn't any actual feedback on how it works yet.
https://www.theregister.co.uk/2018/06/27/windows_10_path_chrome_smb1_patch/ (https://www.theregister.co.uk/2018/06/27/windows_10_path_chrome_smb1_patch/)
-
Kewl, Hope this will help. SMBv1 being old and maybe not as secure, still think MS was too quick to disable it. Way too many devices still using it. ::)