Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I just bought the DNS-323 yesterday and am using (or plan to use) 2 640gb WD drives with it.
I installed the drives, booted the device up and the power light began to blink, eventually the drive lights came on and the network light came on, but the power light never stopped blinking. The unit doesn't self-power down if I hold the power button (even for over a minute) and the reset button on the back doesn't do anything.
I can see the device get a DHCP lease and then drop it, then get it again over and over again, but I can never connect to the web interface or use the utility to see the device.
Do I just have a bad unit? Can I flash the firmware (factory installed with 1.04) in it's current condition to try to fix it?
Should I just RMA it and hope for a working unit?
Thanks.
Offline
Try powering it up without the drives or with just one drive and see what happens.
Offline
Tried that, got the same behavior.
Offline
Try powering up without the network cable plugged in. This assigns a static IP to it. If it makes it through the boot, check your network for problems (cable and/or voltages on the wire). If it continues to act the same, RMA it.
Offline
I tried your suggestion and without drives in it did stop blinking, which I assume means it completed its initialization. I plugged it into the network at that point but still could neither navigate to it or browse to it with the utility. I'm using the stock ethernet cord that came in the box, maybe it's messed up, I'm plugged into the same hub as my main desktop, and that works fine, as do all the other network devices in the house. Maybe it's the cable? That would seem pretty random though.
Offline
What subnet is your main computer on? The static IP that would have been assigned to the DNS is 192.168.0.32. Your computer needs to be on the same subnet as this in order to access it.
Offline
My computer is 192.168.1.104 or thereabouts, the router is 192.168.1.1, the subnet masks are all 255.255.255.0. There's no reason to think that this is the issue. I'm plugged into the same local switch/router as my desktop, which does work, and now using a cable that has no issues with other devices. The device does boot if I turn it on without the connection to the network, but it still doesn't reboot if I use the button on the back or turn off if I try the button on the front. I think therefore it's still RMA bound unless anybody has a better idea.
Offline
That is exactly the issue. You are on a different subnet. Since it boots up without the network cable in, it will have an ip address of 192.168.0.32. That is on a different subnet than your machine (192.168.1.104). You need to set the ip manually on your computer to 192.168.0.something in order to log into the DNS admin page. The fact that it is plugged into the same physicalhardware is not relevant. Try that first. As for the buttons, it does not reboot with the one on the back, and the one on the front caan be finicky, so those currently are not clear cut indications that there is problem. There are a few ther people here that have had problem with their DHCP servers giving a good address to the DNS.
Offline
Thank you for your help, I was able to get it too boot up, connect to my computer, and reset the default IP to a 192.168.1.xxx subnet, and now everything works great.
I appreciate it, you saved me the hassle of returning a perfectly good device, and I look forward to using it more. Thanks again.
Offline
Goog, glad to hear it is working.
Offline