Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Horinius]

I bought my DNS320L maybe two years ago.  Then I found that the product has already been discontinued by D-Link!

And then recently Microsoft will disable its support in future Win10.

So, what option does it leave to us?  I'm not willing to throw my DNS320L out of the windows!  I had paid about $400 (the device + two discs).

[FurryNutz]

Correct, However MS said they were going to help solve the SMB1 in Windows 10:
http://forums.dlink.com/index.php?topic=65722.0

Just enabling SMB1 in Windows 10 resolves connection issues...

[miko8888]

I add this for documentation purposes if somebody else reads this post. You can get smbv2 with the alternative open source firmware ALT-F https://sourceforge.net/projects/alt-f/ that works on the DNS320L. I followed the instructions here: https://sourceforge.net/p/alt-f/wiki/How%20to%20Use/ and smbv2 works well on  my own DNS320L.

[Horinius]

Correct, However MS said they were going to help solve the SMB1 in Windows 10:
http://forums.dlink.com/index.php?topic=65722.0

Just enabling SMB1 in Windows 10 resolves connection issues...

Forcing people to use an old, and most importantly unsecure, protocol is called a solution?  I think we need to go back to the definition of the word solution.

[FurryNutz]

IF users are concerned about using an old protocol, then users will need to look into getting in to newer generation NAS. The DNS line is EOL and D-Link is no longer coming out with newer models. Unless there is a major security issue found with DNS, like with the Cryptor problem that D-Link fixed, D-Link is no longer putting out regular FW updates.

I personally have never seen any issues with using SMBv1 ever in all the years of using it. For those that have DNS, NFS is available as an alternative solution for SMBv1 using there DNS if you have concerns about using your DNS.

Good Luck and enjoy.

[ivan]

I would add to what FurryNutz says.  SMB v1 is only potentially unsafe if the units using it are directly connected to the internet (by directly connected I mean there is no firewall or other protection like a fully manage switch between the unit and internet).  If you leave yourself wide open you can expect the bad guys to come calling no matter how good your security is.

If you are really concerned get a tpLink VPN unit with a firewall and put your network behind that - make sure you set up adequate firewall rules and set it to log all attachment attempts.

[FurryNutz]

Nobody is forcing anyone to do anything.

Correct, However MS said they were going to help solve the SMB1 in Windows 10:
http://forums.dlink.com/index.php?topic=65722.0

Just enabling SMB1 in Windows 10 resolves connection issues...

Forcing people to use an old, and most importantly unsecure, protocol is called a solution?  I think we need to go back to the definition of the word solution.

[OmegaMan]

 > Nobody is forcing anyone to do anything.

Yes true, but neither is anyone forcing D-Link to support its old products... I've discovered that a work PC cannot access either of my D-Link Nas-es while on my intranet due to security policies on the pc. 

I choose D-Link because (at the time) they were keeping up with the updates for a NAS I bought in 2010-ish. If there is a work-around, *as provided by D-Link* which can be done, please let us know.

[FurryNutz]

Been told that NFS configurations would be an alternative.

Keep a PC, windows 10 or 7 on hand for access of NAS. Something you can keep SMB1 enabled.