Print

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

[Bearded]

Hardware version is B1
Firmware 1.10
I'm located in Canada
and yes I have both SMB v1 Client and Server  enabled

[FurryNutz]

I presume this is a MS update issue.
What the DNS accessible before the update?

[Bearded]

I had issues with one of the hard drives and stopped using the DNS-323 for a bit, I have since upgraded my computer to windows 10 and I'm at update 1803.
I replaced both hard drives and started using the NAS again, so I'm unfortunately unable to say if this problem results from an update to Windows 10.
But when I boot into windows 7, everything is fine...

[Bearded]

Fixed the problem!
opened Settings / Network & Settings / did a Network Reset and let the computer reboot
that fixed it???
not sure what was wrong with the network but now my shares work, my mappings work, and I can access the admin page through the browser...

thanks for your help!

[FurryNutz]

Good to hear. Glad you got it fixed. Thanks for letting us know what the problem was.

Enjoy. 

[YaNKee]

So if I have enabled the SMB1 on my Windows 10, and when I use the DLink discovery tool, it shows the device, then I see the "Volume_1" at the bottom, but when I select it and click Connect, it says "Failed to Map drive".  Is this a result of this SMB1 being disabled?  I have had these drives working for years, and all of a sudden I just lose all of my data because Windows doesn't support the protocol? 
I am devestated.  I just lost about 6 TB of media files.  Is there NO WAY to recover what is on these drives?

[FurryNutz]

You need SMB1 enabled in Windows 10:
http://forums.dlink.com/index.php?topic=65722.0
http://windowanswers.com/windows-rt/windows-10-falls-to-access-network-drives-297748.html

[YaNKee]

Yes.. I enabled it in Windows 10, and the drive shows under the mapping tool, but when I click Connect, it says FAILED TO MAP DRIVE.  It doesn't work.

[FurryNutz]

Use \\IPaddressofDNS\Volume_# to map the drive...

[YaNKee]

When I try to do that, it says Windows cannot Access //IPAddress/Volume_1 ...  Check the spelling of your name or there might be a network problem. 

This is the DNS323 where it actually recognizes the drives from the Device Disk Tools, and says it has 2 x 1TB drives.  I ran the disk check on it, and after about 2 hours everything seemed fine.  It made it to 100% and then put me back to the login screen. 

Any other idea?  Should I be installing some sort of 3rd party RECOVERY software to try and get the info back?  I really wish I hadn't striped them.  What a mistake.  But then again, financially it wasn't feasible at the time.  I don't think using a 2 bay device for RAID is even possible otherwise.  I think 3 is the minimum isn't it for being able to recover a drive if one goes down?

[FurryNutz]

Try with back slashes. That was a typo on my part. Sorry. 

[YaNKee]

I tried with backslashes...  I get a weird result now...  Here is the screen it comes up with now.
https://imgur.com/a/oSfGM7r

Not sure what to do now.

[FurryNutz]

What happens when you type that string in to the map drive window? It should come with with a log in screen.
Has the DNS worked before with Windows 7?

[YaNKee]

Yes absolutely.  This worked with my computer for years.  I think I started at Windows XP, and moved all the way up to Windows 7.  I think it worked with Windows 10 up until a few months back..  I turned the drive off since I was not using it and about 3-4 months later when I turn it on, it just doesn't do anything anymore.

[FurryNutz]

Can you find or barrow a Windows 7 PC or laptop to see if the DNS still works there? Seems that if it worked on Windows 10, MS may have messed something in in one of there updates maybe.

Trying a WIndows 7 PC will check to see if it can connect or not. If not, then something maybe wrong with the DNS. A reset maybe needed.