D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: w9ndb on January 09, 2011, 11:16:54 AM
-
I have a DNS-323 that I've been using for about a year with minimal issues, recently I relocated it to a different part of my house (same LAN) and since then it will not obtain a DHCP lease from my DHCP server.
All other machines operate normally and I'm 99.999% sure that this is a problem with the DNS-323. I've tested cables, used known good machines on the segment and even moved the NAS back to it's original location/cable and it exhibits the same behavior, requests a dhcp lease, dhcp server sends a reply and the NAS just ignores it (I've sniffed the connection and watched the transaction).
I can get into the NAS with the default IP of 192.168.0.32 if I configure a machine onto that subnet, but I'm unable to assign a static IP (the NAS takes it and then just resets to 192.168.0.32/24 after I apply). I've also tried resetting to default, downgrading from 1.09 to 1.08, resetting 1.08 to default and even running fun_plug to get a shell.
Once I have a shell on the box I can manually ifconfig the address I want, but after a short time it reverts to the 192.168.0.32/24 address again.
Has anyone seen this bizarre behavior before? Are there any ways to repair it? I've done everything I can think of short of hacking the rc files to use my address instead of the default 192.168.0.32/24, which I'd rather not do since this seems indicative of a larget problem.
TIA,
nb
-
I can't be the only one to have seen this behavior. Anyone? Bueller?
-
Sorry never seen that.
-
Mh, did you make a hard reset via the button on back side? Maybe there's some sort of misconfiguration stored (the kind which you can't access from UI).
//Hsishi