Print

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

[wake]

My DNS-321 seems to be shutting off after being inactive for some amount of time. For testing I have hard drive hibernation disabled, UPnP AV Server disabled, iTunes Server disabled, DHCP Server disabled and LLTD disabled. Could anyone shed some light as to why it seems to power down?

As an example, I used it a couple of days ago and today I couldn't get to the admin page or ping the device. Went to the device and there are no LEDs on, it's cold as can be, completely off. I hit the power button and it boots up and everything is great. I'm currently on 1.01.

Thanks

[wake]

After doing some thinking, I might have a reason as to why this is happening. The DNS-321 currently obtains its IP from the router via DHCP. The router has a DHCP Lease Time of 24 Hours. I'm wondering if the router is taking back the IP after 24 hours of inactivity and the DNS-321 is then shutting down? I can configure it with a static IP to test this theory.

[Freeman]

Check your email alert settings. You may have checked the box for the temperature threshold. If the DNS passes the set temperature it will shut down.

[fordem]

After doing some thinking, I might have a reason as to why this is happening. The DNS-321 currently obtains its IP from the router via DHCP. The router has a DHCP Lease Time of 24 Hours. I'm wondering if the router is taking back the IP after 24 hours of inactivity and the DNS-321 is then shutting down? I can configure it with a static IP to test this theory.

Let me know what happens with the static ip - it's very unlikely that this is in anyway related to the ip addressing - based on how DHCP works, the router will not "take back" the ip address.

[D-Link Multimedia]

Also the unit will not shut off due to not receiving an ip address. It has an internal hardcoded ip of 192.168.0.32 by default if it doesn't obtain DHCP. Sounds like a power or heat issue.

[wake]

Thanks all, email notifications were turned on and it was in fact reaching the temperature limit. The hard drives have now been placed back in suspend mode so we'll see what happens from here. Thanks!

[palswim]

I'm seeing something similar.  My unit doesn't completely shut down, it just seems to forget to respond to its name.  Even in DHCP, it still seems to maintain its lease.

But, I've given it a name, and then from my Windows boxes, I can ping that name and connect to it via the Web Interface.  After a while, it just stops responding to that name, but I can still access it by its IP address.

So, some service seems to shut down after a while.  DHCP seems like it works, since it maintains its address and entry in my router's DHCP list.  But, I'm wondering if a NetBIOS service or something similar decides to take a break after a couple hours of work.

[gunrunnerjohn]

palswim, your symptom doesn't sound like anything I've ever seen, I'd have to believe this may be a hardware issue.  I've run firmware 1.01, 1.02, and 1.03, and this has never happened.  I can't see this being a firmware issue.