Author
Topic: D-Link DNS-323 not discovered after upgrade to Windows 10 (Read 73556 times)
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.
Logged
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
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?’.
Logged
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.
Logged
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.
Logged
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.
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.
Logged
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
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.
Logged
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.
Logged
This is a known problem acknowledged by Microsoft:
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.
« Last Edit: October 10, 2016, 02:33:52 PM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.
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
Logged
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.
Logged
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.
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.
Logged
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.
« Last Edit: March 31, 2018, 10:43:20 AM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.
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
Logged
Link>Welcome!
- What Hardware version is your DNS? Look at the sticker behind or under the device.
- Link>What Firmware 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
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 worksAnyone find a solution to this with Windows 10?
Under Windows 7 everything works fine
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.
Автор
Mutabor
Здравствуйте, моя домашняя сеть подключена к ботсети. Я узнал об этом из Касперского, зайдя в мониторинг умного дома увидел, что к моей домашней сети подключено 250 устройств.
Ранее хакер взломал мой роутер и почту, поменяв пороли. Я все пароли поменял,
на сложные, использовав генератор паролей, на почту смог войти по отпечатку пальца через смарфон, а роутер перезагрузил.
Для того чтобы выйти из этой бот сети я создал в роутере белый список, привезав мак адреса моих устройств, так же создал гостевую сеть и перенаправил в нее устройства которые не поддерживают шифрования WAN 3 personal, это две колонки Алиса и телевизор. Три устройства поддерживающие это шифрование я оставил в основной сети. Это два смартфона и андроид телевизор.
После этого Касперский показал что я вышел из ботсети, однако на следующее утро я снова увидел, что являюсь её участником.
Так же на компьютере Касперский пишет, что у меня открыт 22 SSH порт, как его закрыть на моем роутере TP-Link Archer C80 я не знаю, перерыл всё меню. интернет, задавал вопрос ии, ответа так и не нашёл.
Хотя я заходил на https://www.yougetsignal.com/tools/open-ports/ чтобы проверить открыт ли этот порт у меня, пишет что порт закрыт.
Осталась единственная надежда на вас, может вы сможете помочь, пожалуйста помогите выйти из этой ботсети.
Сообщения без ответов | Активные темы
| Автор | Сообщение |
|---|---|
|
Заголовок сообщения: DNS-323 не доступен по сети Добавлено: Пн фев 01, 2010 19:14 |
|
|
|
Здравствуйте! Замучил такой глюк: частенько бывает после включения оборудования DNS-323 не доступен по сети. Настроен доступ по FTP и по SMB протоколу. Устройство недоступно, ни по сетевому имени ни по IP-адресу. Через WEB-интерфейс доступен только по IP-адресу. На данный момент IP-адрес статический, раньше был динамический. Устройство подключено к роутеру DLINK DIR-615. Лечится глюк так — если зайти в настройки через WEB-интерфейс в раздел «Device» (там где сетевое имя устройства устанавливается) нажать на кнопку сохранения настроек, сразу все становится нормально. Но это не выход, хотелось бы избавится от этого досадного глюка. Спасибо. |
| Вернуться наверх |
|
|
dillan21rus |
Заголовок сообщения: Добавлено: Пн фев 01, 2010 19:20 |
|
|
чем настраивали? IE? или каким нить другим браузером? _________________ |
| Вернуться наверх |
|
|
sv18253 |
Заголовок сообщения: Добавлено: Пн фев 01, 2010 19:29 |
|
|
dillan21rus писал(а): чем настраивали? IE? или каким нить другим браузером? Оперой |
| Вернуться наверх |
|
|
dillan21rus |
Заголовок сообщения: Добавлено: Пн фев 01, 2010 19:31 |
|
|
sv18253 писал(а): dillan21rus писал(а): чем настраивали? IE? или каким нить другим браузером? Оперой мой последний пост почитайте вот здесь _________________ |
| Вернуться наверх |
|
|
sv18253 |
Заголовок сообщения: Добавлено: Пн фев 01, 2010 19:59 |
|
|
dillan21rus писал(а): sv18253 писал(а): dillan21rus писал(а): чем настраивали? IE? или каким нить другим браузером? Оперой мой последний пост почитайте вот здесь Есть сомнения, что поможет. Настройки то сохраняются и глюк не постоянный. Бывает после загрузки все ОК работает. Попробую сохранить настройки через IE. |
| Вернуться наверх |
|
|
dillan21rus |
Заголовок сообщения: Добавлено: Пн фев 01, 2010 20:08 |
|
|
я сам думал что настройка мазилой и IE ничем не отличаются, а хотя ошибся, разница есть, в т.ч. и опыт))) _________________ |
| Вернуться наверх |
|
|
sv18253 |
Заголовок сообщения: Добавлено: Чт фев 04, 2010 20:54 |
|
|
К сожалению не помогло. Спасибо. |
| Вернуться наверх |
|
|
Mikhnevich Roman |
Заголовок сообщения: Добавлено: Ср фев 10, 2010 18:16 |
|
|
|
| Вернуться наверх |
|
|
sv18253 |
Заголовок сообщения: Добавлено: Ср фев 10, 2010 22:39 |
|
|
Mikhnevich Roman писал(а): какая прошивка ? 1.08b08 beta |
| Вернуться наверх |
|
|
Mikhnevich Roman |
Заголовок сообщения: Добавлено: Вт фев 16, 2010 17:29 |
|
|
sv18253 писал(а): Mikhnevich Roman писал(а): какая прошивка ? 1.08b08 beta попробуйте обновиться до 1.08 релиз версии |
| Вернуться наверх |
|
|
pavlundiy |
Заголовок сообщения: Добавлено: Вс мар 07, 2010 00:08 |
|
|
Такая же беда. Но помогает только выключение и затем включение питания DNS-323. Больше никак не лечится. Прошивка 1.08 |
| Вернуться наверх |
|
|
BelousovMP |
Заголовок сообщения: Добавлено: Вт мар 09, 2010 07:55 |
|
|
У меня установлена последняя прошивка 1.08, однако также наблюдается проблема с сетью. Проблема в следующем: |
| Вернуться наверх |
|
|
babahus |
Заголовок сообщения: та же проблема Добавлено: Вт мар 09, 2010 09:41 |
|
|
DIR-300 NRU + DNS-323 + WI-FI (Mac Bookpro) После перезагрузки DNS-323, macbook не видит сетевого диска Через вэб я на наего захожу даже торрент качает но на компе нет проходит время находится сам — систему когда и почему не выяснил все устройства к роутору через DHCP — рабоча группа по умолчанию workgroup я так понял у всех такая проблема — хотелось услышать коментарии от специалистов с dlink |
| Вернуться наверх |
|
|
Fragir |
Заголовок сообщения: Добавлено: Сб мар 20, 2010 10:05 |
|
|
Абсолютно та же фигня-с. После включения наса сетевой диск то доступен, то нет. По ip — пожалуйста. «…зайти в настройки через WEB-интерфейс в раздел «Device» (там где сетевое имя устройства устанавливается) нажать на кнопку сохранения настроек, сразу все становится нормально». Вот только, боюсь, комментариев от специалистов от D-Link мы не дождемся… _________________ |
| Вернуться наверх |
|
|
Olegavb |
Заголовок сообщения: Добавлено: Сб мар 20, 2010 13:22 |
|
|
Fragir писал(а): Абсолютно та же фигня-с. После включения наса сетевой диск то доступен, то нет. По ip — пожалуйста. «…зайти в настройки через WEB-интерфейс в раздел «Device» (там где сетевое имя устройства устанавливается) нажать на кнопку сохранения настроек, сразу все становится нормально». Вот только, боюсь, комментариев от специалистов от D-Link мы не дождемся… Аналогично — случается периодически такое. _________________ |
| Вернуться наверх |
|
Кто сейчас на форуме |
|
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 7 |
| Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения |
-
#1
Hi experts,
I need some help to connect to my Dlink NAS 323 on Windows 10.
I am running Windows 10 Version 1903 for x64
I have enabled all the SMB1 and allowed private sharing on my comp.
However, I am still unable to even see my NAS using 192.168.0.1 and it does not appear on my files explorer, so totally no way to map it.
Is there any expert that can help?
-
#2
Set ‘Enable file sharing for devices that use 40 or 56 bit encryption’
-
#3
Set ‘Enable file sharing for devices that use 40 or 56 bit encryption’
just tried but still unable to find see the NAS on my Windows 10
-
#4
Can ping and access NAS UI?
Perhaps it’s high time to ditch the stock firmware and go for 3rd party like Alt-F.
-
#5
Can ping and access NAS UI?
Perhaps it’s high time to ditch the stock firmware and go for 3rd party like Alt-F.
No. Tried to ping the NAS. no response at all and got Timeout.
likewise when I went to the IP address of the NAS.
-
#6
No. Tried to ping the NAS. no response at all and got Timeout.
likewise when I went to the IP address of the NAS.
If NAS is inaccessible in the first place then the issue has nothing to do with SMB, fix the NAS IP address problem first.
-
#8
192.168.0.1 <- is that the NAS IP? looks like a default router IP. Likely the NAS is on a DHCP assigned IP or a separately configured IP. A quick Google search shows default as 192.168.0.32? http://files.dlink.com.au/products/DNS-323/REV_C/Manuals/v1.3/DNS-323_Manual_v1.3.pdf
I tried 192.168.0.32, also not accessible. Ping this IP also getting time out.
Even with the NAS turned on, on my network, I can only see my computer and the router.
Basically, the NAS was working fine on my old WIN 7 machine until I changed to a new laptop recently which had WIN 10.
Searching the web, almost all websites stated that I need to turn on the SMB1 under windows feature which I had done so and was expecting to see the NAS.
But somehow, I am unable to even see the NAS in my home network when when it is connected to the router on cables physically
-
#9
If NAS is inaccessible in the first place then the issue has nothing to do with SMB, fix the NAS IP address problem first.
Would you be able to share how to do it? I am unable to access the NAS, so not sure how to do it via my comp
Sorry, I am not too networking savy
-
#10
It’s prob on another IP address I am guessing.
— Reboot the NAS
— Go into your router admin page -> look for any network map or IP address assignments and see if you can identify the NAS IP
-
#12
Got it. Thanks!
The direct mapping from Microsoft didn’t work at all. After I downloaded everything from there, think it is time to change to USB drives.
-
#13
If you can’t even see your Dlink NAS 323 in the router page, consider plugging the NAS directly to your PC to check if the cable/nic port is faulty
Hi experts,
I need some help to connect to my Dlink NAS 323 on Windows 10.
I am running Windows 10 Version 1903 for x64
I have enabled all the SMB1 and allowed private sharing on my comp.However, I am still unable to even see my NAS using 192.168.0.1 and it does not appear on my files explorer, so totally no way to map it.
Is there any expert that can help?
Synology NAS Device is one of the most secure file-level architecture for storing and sharing a significant amount of data. This high-capacity storage device can be easily connected to your home or office networks though WI-FI or LAN. Multiple users and heterogeneous client devices can store, access, and recover data from a centralized storage (NAS), which appears in your Windows system as a shared network device.
Unfortunately, there are times when you may experience NAS device visibility issues in Windows Explorer. This problem worsens when you provide the correct password to access the Network Attached Storage device but receive an error instead. NAS Device Not Visible error occurs while you’re trying to access your Synology NAS and the access is blocked.
What Causes NAS Device Not Visible Error?
The common reasons behind the error are SMBv1 not being enabled on the system, incorrect network proxy settings, network discovery being turned off, corrupt IP or DNS cache, or a third-party firewall interfering with the connection. The error is mainly affecting Windows 10 and 11 users as per most tech forums.
Older versions of Windows are not typically affected by this error. Microsoft has disabled the Server Message Block (SMBv1) protocol on Windows 10 and 11 due to security reasons. The error occurred after the Fall Creators Update, version 1709, or Windows reinstallations.
How to Fix NAS Drive Not Showing on Network Error?
Although advanced methods to fix the NAS drive not showing on network in Windows 10 and 11 exist, below are some quick fixes you can try!
Quick Fixes
- Turn on network discovery by following Control Panel > Network and Internet > Network and Sharing Center > Change Advanced Sharing Settings > Turn on network discovery > Save changes.
- Edit Group Policy by accessing Group Policy Editor > Computer Configuration > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons > Enabled > OK.
However, the above-shared quick fixes are only impactful in limited scenarios. Hence, if you fail to solve the NAS device not visible error on Windows 10 and 11, try the proven methods shared below!
Methods to Fix NAS Device Not Visible on Network
To fix the NAS device not visible on Windows Explorer error, try the methods discussed below. Carefully follow the steps and notes, wherever mentioned!
#1 Enable Windows Network Discovery on Synology NAS
This method applies to Synology NAS running DSM 6.2 or above versions or computers with Windows Vista or later versions. You can enable the Windows Network Discovery to allow file access via the SMB checkbox at one of the following locations in the DSM:
For DSM 6.2:
- Open the Control Panel and locate File Services.
- Open File Services, go to the SMB tab and then select WS-Discovery.
For DSM 7.0:
- Go to Control Panel and open File Services.
- Next, go to the Advanced tab and open WS-Discovery.
#2 Enable Local Master Browser on Synology NAS
In case your Synology NAS is running 6.1 or below versions, or the system has older versions of Windows installed, enable the Local Master Browser with the following steps:
For DSM 6.0 and 6.1:
- Open the Control Panel, go to File Services, and locate the SMB/NFS/AFP tab.
- Next, go to SMB and click Advanced Settings.
For DSM 5.2:
- Follow Control Panel > File Services > Win/NFS/Mac tab.
- Further, go to Windows File Service > Advanced Settings.
#3 Enable SMBv1 on Windows 8.1, 10, and 11
If your NAS device needs the SMBv1 (Server Message Block version 1) network protocol to communicate over the network, you can try this method. Enable SMBv1 with the following steps:
- Access Windows Search by pressing Windows + S, and type Control Panel to open it.
- In the Control Panel, select Programs > Programs and Features.
- There, click Turn Windows features on or off.
- Thereafter, locate SMB 1.0/CIFS File Sharing Support and select the checkbox given against it.
- Click OK to apply the changes. Finally, click Restart now and check if you can access your NAS on your system after reboot.
Note: SMBv1 is no longer available in Windows 10 and later versions except in Home and Pro editions; Microsoft advises against installing the SMBv1 protocol. Instead, update the SMB server, which is still required.
#4 Enable NetBIOS Service on your System
You can also enable the NetBIOS service on your system and see if it fixes the NAS device not visible error on the Windows system. Follow the given steps:
- Go to Control Panel, and follow Network and Internet > View network status and tasks.
- Next, change the adapter settings, click Change settings for this connection, and select the connection you’re using.
- Double-click Internet Protocol Version 4 (TCP/IPv4) in the ‘This connection uses the following items list.
- Click the Advanced button and go to the WINS tab.
- Select Enable NetBIOS over TCP/IP and click OK on every window to save all the settings.
Once done, check if the Local Master Browser is enabled on your Synology NAS. Re-enable the network discovery by following Network and Internet > Network and Sharing Center > Change advanced sharing settings.
Turn off network discovery under the Network discovery section and clear the DNS cache.
#5 Reset Synology NAS
If you’ve performed all the methods and are still unable to fix the NAS Device Not Visible error on the Windows system, try resetting your Synology NAS with the following steps:
- Ensure your Synology NAS and system are in the same local area network and subnet.
- Disable or temporarily remove the firewall software from your system.
- Use a different Ethernet cable to connect to the Synology NAS to look for the defective wires.
- If the NAS device has multiple network ports, connect the Ethernet cable to that port to identify the defective ports.
- Finally, press the RESET button on the back of your Synology NAS for four seconds or until you hear a beep sound. You can also refer to this guide to learn to reset Synology NAS.
Final Words:
Synology NAS device is an excellent data storage and file-sharing solution. However, it’s not immune to errors such as NAS devices not visible. The error makes your NAS invisible, blocking access to your files. Even though the files can be recovered if you have NAS backup or a reliable NAS data recovery software available, fixing the issue needs a proper approach. Another quick solution to fix the NAS device not visible on Windows 10 and 11 devices could be mapping the shared folder to a drive letter to show NAS under Network Devices on the system. Try the solutions and tell us which solution helped you overcome the issue.
People Also Ask
Q. How do I assign an IP address to my NAS?
You can set up the IP address of your NAS manually by following NAS WebUI > Control Panel > Network → TCP/IP > General Settings > DNS server > Provide a server entry > Apply.
Q. Is Synology better than QNAP for NAS setup?
Where QNAP can only handle traditional RAID drives, Synology NAS supports Synology Hybrid RAID. Additionally, QNAP supports EXT4 formatted devices, while Synology offers EXT4 as well as the latest B-Tree File system. There are several other factors that you may consider while choosing between Synology and QNAP for NAS setup.
Q. Are RAID and NAS the same?
RAID is a set of multiple hard drives configured to function as one logical unit to deliver performance, redundancy, or both. NAS is a file-level data storage architecture, connected over a local-area network or Wi-Fi, providing a single access point to store and share files easily.