Print

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

[Yurym]

Last week I noticed DNS-323 activity when nobody was supposedly connected to it.

Is it possible to understand what process caused this disk I/O?

DNS-323 was bought about 3 years ago and still has 1.3 firmware.
I have RAID 1 with two identical HDDs.

It's a home network behind DIR-615 in a default configuration.
I noticed "paleolithic" user on DNS-323 and deleted it. I have also changed an admin password on DNS-323.

I did not notice any way to determine who/what cuased I/O using standard 1.3 GUI.
Does new GUI v.1.9 provide more information about DNS-323 usage?

[jamieburchell]

My primary concern would be the user account that was added without your knowledge. The question is, can someone access your NAS from outside your network (firewall), or inside (breached wireless network, breached cabling).

If your NAS is exposed, it's entirely possible that unauthorised access is keeping it awake.

Other considerations could be: Access to the FTP server wakes up the NAS even before authentication, scheduled downloads, Bit torrent, other device on your network communicating with the NAS.
When my other half switches her laptop on, our NAS wakes up, I have no idea why but it could be the shortcut she has to it on the desktop resolving, or a network service.

[Yurym]

Access to the FTP server wakes up the NAS even before authentication, scheduled downloads, Bit torrent, other device on your network communicating with the NAS.

Now I have disabled all servers on DNS-323, however sometimes I see DNS-323 access I do not understand.
I do not see any "IN" connection on DIR-615 at that time.
I do not have any scheduled download.

... Bit torrent, other device on your network communicating with the NAS.
When my other half switches her laptop on, our NAS wakes up, I have no idea why but it could be the shortcut she has to it on the desktop resolving, or a network service.

I would like to investigate these options.
Would firmware 1.9 provide more tools for this investigation?

I will run netstat on a computer of my son. DNS-323 access typically happens when he is using his laptop.

P.S. So far I have no enthusiasm to install a custom Linux OS for DNS-323 (fun_plug etc.).

[jamieburchell]

I do not think updating the firmware will help you to trace the problem, but upgrading firmware is generally a good thing to do, especially if you are having issues. You should perform a factory reset after upgrading the firmware and re-configure manually. Note you shouldn't loose any data but a backup is recommended.

[lookingforinfo]

Jamie,

Should Yurym perform the firmware upgrades one at a time with a factory reset and manual re-configuration after each update, or can Yurym go from 1.3 to 1.9 and do the reconfiguration only once?
Your answer could help others either save work or avoid more problems.

[jamieburchell]

It is not necessary to apply the in between upgrades. Each firmware file (at least up to 1.09) is it's own complete version.

I don't think a factory reset after a firmware flash is documented, but many have found it to resolve strange issues. A school of thought is that legacy or incorrect configuration values might be stored from the previous firmware. We also say to configure manually rather that from a backup file incase the actual format of the config file has changed between firmware versions, or if values have been added or removed.

It's strange, but in many cases a factory reset sorts problems out, hence my signature. It would be nice for D-Link to comment on why that might be.

Other manufactures say to perform a factory reset after a firmware change, for the reasons I have mentioned.