D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: 4merSunSE on January 21, 2016, 08:13:35 AM
-
My venerable DNS-323 is not discovered after I upgraded to Windows 10. I attempted to connect to it with my original IP address and the default IP address, http://192.168.0.32/, but Firefox, Edge, and Chrome all time out.
Is there something I should know about this appliance and Windows 10?
My DNS-323 is hardware version C1 and came with firmware version 1.08. I've upgraded the firmware; but, I don't know what version I'm at now; because, I can't access the appliance.
-
It is nothing to do with your DNS-323 but it has everything to do with win 10. We found this out last weekend the hard way when one of our clients office computers updated to win 10 and then wouldn't/couldn't do their weekly backup to the NAS boxes on site or in our computer room.
There is a problem with SMB/CIFS implementation in win 10 and I assume there will be a fix for that soon. The other thing you need to do is check that your NAS and win 10 computer are in the same workgroup and that win 10 is correctly setting your computer to the correct network subnet.
This item my service manager found might be of help http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer-9.html (http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer-9.html)
For those interested we solved the clients problem - since they office computers and using things like LibreOffice for the bulk of their work, after we managed to recover the last days work we reformatted the drives and installed Linux Mint and the Linux versions of their software. We have had only one complaint and that wes 'why didn't we do that sooner?'.
-
Thanks for the reply and the link; I'll check it out now; and maybe look at a MSFT board to see what's up there.
As for the workgroup and subnet; they should be. Win 10 maintained the same workgroup in the upgrade, and I made no changes to the DNS-323 before the upgrade. Of course, I don't know for sure, because I can't access the NAS.
Do you think trying the DNS-323 USB connection might work; just to make sure everything is copacetic on it; or, is that even possible?
Thanks again.
-
I'm sorry that I can't be more specific at the moment but I do have one of my people trying to find out what win 10 does to networking to stop the local network being seen.
All I can think of at the moment is that, if you have a tablet (we use Android tablets but I assume the Apple tablets can do the same things) use something like ES File Explorer and look under the 'Lan' or 'FTP' tabs and you should see your DNS-323 and can check that everything is in fact still there (with the FTP you will have to put in the IP address of the NAS, assuming you have FTP activated). You should also be able to open the web UI using the tablets built in browser.
-
Ivan,
Your suggestion to try an Android tablet was great! The DNS-323 shows up fine and I could find and access the file I was looking for. 8)
Now I'll have to try and figure out why Windows 10 doesn't see it. I made sure the workgroup name matched, but have now other ideas to try right now.
-
We came across the same problem with in the DNS-320 forum. There is a solution for this time http://forums.dlink.com/index.php?topic=65605.0 (http://forums.dlink.com/index.php?topic=65605.0)
I don't know if it was a genuine mistake on the part of MS of if they have gone back to their old ways of 'embrace, extend and extinguish', I do know they are pushing very hard for people to take up their Asure cloud offering.
-
I'm really new on that and I need a really easy level explanation to understand what can I do.
I have a D-LINK DNS-323 (B1) and after updating to Windows 10 I cannot open it. When I click over the icon, I'm always sent to the URL bar to access through the IP address but I do not have any "username" and "password".
I've change my computerīs name and workgroupīs name and itīs not working (I got other computers with Windows Xp, Vista, 7 and 8 and works perfect).
What do I have to do to access to it?
Thank you.
-
This is a known problem acknowledged by Microsoft:
http://forums.dlink.com/index.php?topic=65722.0 (http://forums.dlink.com/index.php?topic=65722.0)
I'm really new on that and I need a really easy level explanation to understand what can I do.
I have a D-LINK DNS-323 (B1) and after updating to Windows 10 I cannot open it. When I click over the icon, I'm always sent to the URL bar to access through the IP address but I do not have any "username" and "password".
I've change my computerīs name and workgroupīs name and itīs not working (I got other computers with Windows Xp, Vista, 7 and 8 and works perfect).
What do I have to do to access to it?
Thank you.
-
I have a DNS-323-A1 with WIndows 10. I was able to connect by running the DLINK Easy Search utility and assigning a drive letter to each volume. Hope this helps
-
Something to do with SMB 1.0 for Windows 10 security. They removed the SMB 1.0 automatically.
Go to Windows Feature and turn it back ON.
(https://image.ibb.co/miCjMS/Capture.jpg)
-
Thank, we hope this will be helpful for future users.
There is a FAQ posted here as well:
http://forums.dlink.com/index.php?topic=65722.0 (http://forums.dlink.com/index.php?topic=65722.0)
-
Wouldn't it be more prudent to configure the 323 to use Samba server v3, rather than enable Samba client v1 in Windows 10? It's disabled on Windows 10 for a reason, security.
-
It's only MS security issue which they chose to not fully support, however it's still available in there OS so might not be a major concern.
The 323 has been out of service and no longer developed on. EOL. Unless there is a major security flaw that needs fixed, there probably won't be any more FW updates.
STATUS: EOL
This product has been discontinued.
Free support for this product has ended on 05/05/2013
Wouldn't it be more prudent to configure the 323 to use Samba server v3, rather than enable Samba client v1 in Windows 10? It's disabled on Windows 10 for a reason, security.
-
Here we are July 4th 2018 and I've tried everything and nothing has worked so far.
I have Windows 10 and a DNS-323
I can map a drive but cannot navigate the folder structure without my windows explorer freezing up and crashing
I cannot navigate to my admin console using IE, Edge or Firefox,
I can ping it
I've enabled and disabled everything under the sun but yet nothing works
Anyone find a solution to this with Windows 10? :(
Under Windows 7 everything works fine
-
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?
Do you have SMBv1 enabled in windows 10?
http://forums.dlink.com/index.php?topic=65722.0 (http://forums.dlink.com/index.php?topic=65722.0)
Here we are July 4th 2018 and I've tried everything and nothing has worked so far.
I have Windows 10 and a DNS-323
I can map a drive but cannot navigate the folder structure without my windows explorer freezing up and crashing
I cannot navigate to my admin console using IE, Edge or Firefox,
I can ping it
I've enabled and disabled everything under the sun but yet nothing works
Anyone find a solution to this with Windows 10? :(
Under Windows 7 everything works fine
-
Hardware version is B1
Firmware 1.10
I'm located in Canada
and yes I have both SMB v1 Client and Server enabled
-
I presume this is a MS update issue.
What the DNS accessible before the update?
-
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...
-
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!
-
Good to hear. Glad you got it fixed. Thanks for letting us know what the problem was.
Enjoy. ;)
-
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?
-
You need SMB1 enabled in Windows 10:
http://forums.dlink.com/index.php?topic=65722.0 (http://forums.dlink.com/index.php?topic=65722.0)
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)
-
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.
-
Use \\IPaddressofDNS\Volume_# to map the drive...
-
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?
-
Try with back slashes. That was a typo on my part. Sorry. ::)
-
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.
-
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?
-
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.
-
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.