D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: neuwirth on March 28, 2011, 08:10:48 AM
-
I have my DNS-323 connected directly to my DIR-655 router. I changed the setting from autodetect to the gigabit speed. At that point I lost access to the DNS-323. I tried a hard reset using the little button on the back and connected the DNS-323 directly to my Windows XP PC. Still no access. Did I break the thing for good?
-
The user's guide states that the IP address of the DNS-323 will be 192.168.0.32 after a reset to factory settings. Is this correct?
-
If there is no DHCP server for it to get an ip address from - then yes.
-
I have the NAS directly connected to the PC and cannot ping it using address 192.168.0.32. How long to I hold the reset button in to complete the reset? This is all US equipment.
-
Hold the reset for approx 10 seconds should be fine. Also what version of firmware are you using?
-
I am running 1.09 firmware. The hardware is revision B1. The results of the ping to 192.168.0.32 is Destination host unreachable.
-
Did you also make sure that the jumbo settings on your network adapter were turned off?
-
I see no jumbo settings on my network adapters. I hooked the NAS to three PCs in an effort to fix the problem. Two are Windows XP and the third is Windows 7. They all gave the same result.
-
Did you set a static address on the computer?
The destination host unreachable response suggests the computer is on a different logical network to the DNS-323 - if you were pinging an address on the same network and the NAS was unreachable, you'd get a timed out message.
Are the link leds on?
-
I took one of my PCs off the network and hooked a 3' ethernet cable from it to the NAS. Network activity LEDs flash at each connection. When I do a ipconfig /all I get a Autoconfiguration IP address of: 169.254.82.246. This is not anything close to my network IP addresses. I did have the NAS configured with a static IP address. I assume that is long gone since I have tried several times to 'hard' reset the device with the little button on the back.
-
It beats me why people like to complicate a simple thing like this - if your PC has a 169.254 address, you will be unable to ping the DNS-323 at it's default address, because they are in different networks.
Option #1 - use your router's DHCP server and the D-Link ESU.
1) Connect your PC to the router - make sure it gets an ip address from the router
2) Connect the DNS-323 (reset to factory defaults) to your router, and turn it on.
3) When the power LED on the DNS-323 stops flashing and stays on, verify the network LED is on
4) Run the ESU, make sure it is not blocked by any firewall or internet security suite, if necessary, uninstall the security suite.
5) The ESU WILL find the DNS-323, and allow you to set an ip address of your choice, and as long as you set an ip address within your network range, you WILL be able to access it in your web browser.
Option #2 - use router's DHCP server
1) Connect your PC to your router - make sure it gets an ip address from the router.
2) Connect the DNS-323 (reset to factory defaults) to your router, and turn it on.
3) When the power LED on the DNS-323 stops flashing and stays on, verify the network LED is on
4) Log into the router, find the attached devices page (or the DHCP lease page) and find out what ip address has been leased to the DNS-323.
5) Open your web browser and point it to the address obtained in step #4.
Option #3 - use static addressing
1) Connect your PC to a network hub or switch and configure a static ip address of 192.168.0.30
2) Connect the DNS-323 (reset to factory defaults) to your router, and turn it on.
3) When the power LED on the DNS-323 stops flashing and stays on, verify the network LED is on
4) Open your web browser and point it to 192.168.0.32
Leave the network setting at auto - there is NOTHING (other than grief) to be gained by forcing any particular speed.
-
Thanks, Fordem for the reply. I hope to have time tomorrow to try your options. And you were certinly dead on about the grief! I don't know why I messed with a device that was working just fine. Lesson learned. If I ever do anything stupid like that again, you can reach out from the Internet and slap my hands.