Print

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

[sdhome]

I received my DNS-321 yesterday. Everything was going perfectly. I made several configurational changes including a change to a static IP address of 192.168.4.253. Note: no drives installed yet. All of a sudden the NAS disappeared from sight. I tried to reset it to factory defaults by holding the reset buttion in even though I had no idea if this would work. Several hours later the NAS reappeared at 192.166.0.32. I have two questions:
  1. Why would it disappear for several hours?
  2. How does one reset it to factory default when no GUI access

This experience was somewhat tramatic. Hopefully there are some answers out there. Thanks in advance.

[jswashburn]

Everything was going perfectly. I made several configurational changes including a change to a static IP address of 192.168.4.253. Note: no drives installed yet. All of a sudden the NAS disappeared from sight.

Were you still able to ping that IP even though the GUI was not available?

I tried to reset it to factory defaults by holding the reset buttion in even though I had no idea if this would work. Several hours later the NAS reappeared at 192.166.0.32

Resetting back to factory defaults will erase all your settings including static IP entries.

1. Why would it disappear for several hours?

Not sure, but good question. We would need to know more info about your network, PC, and other relevant information surrounding these circumstances.

2. How does one reset it to factory default when no GUI access

There's a small hole labeled "reset" between power and ethernet jack. With the unit on, use a paperclip to press and hold down the button for about 12 full seconds. That should reset it back to factory settings (your data should be safe however).

I would also suggest updating it to the latest firmware revision.

[sdhome]

Thanks alot. It's worth alot to know how to get it back to factory default when one loses GUI access. Why isn't that documented anywhere? It would seem to be a pretty important thing to note.

I didn't try pinging that address, but I think something was there because Firefox said 'Waiting...' then 'Done' which seemed to imply somebody was there. The screen was blank however. I then held down the reset button in the hope that I could put it back to factory default. Eventually I found it again at 192.168.0.32.

I'm intrigued by your reference to updating to latest firmware. I've searched high and low on the Dlink site and can't find the firmware for the DNS-321. Do you happen to have the link? The link inside the DNS-321 doesn't seem to help. I suggest that a new FAQ point users to the correct place on the Dlink site. This seems to be the closest I could get, but no firmware listed, not even V1.00?
   http://support.dlink.com/products/view.asp?productid=DNS%2D321

As far as my network is concerned, both the Dell E1505 laptop running Windows Vista and the DNS-321 were plugged into a Linksys WRT54gs router.

[ECF]

Reseting it and getting an IP of 192.168.0.32 tell me that your DHCP server is is using IP's in the 192.168.0.xx range so you PC must be in this range as well. Setting your DNS-321 to the IP of 192.168.4.253 put it our of the IP range of your PC there for loosing connection. Try setting it statically to a 192.168.0.xx IP address and you should be fine. As for you resetting issue it looks like it just was not resetting properly you may need to hold the button for a few seconds.

[sdhome]

Actually the chronology was as follows. I received the DNS-321 at a location other than where my network is located, so I connected it directly to PC with PC set to 192.168.0.1. It worked in that mode without problems for a few hours. I then relocated to the site of my network and set IP statically to 192.168.4.253 since the LAN of my router is 192.168.4.x. It worked for several more hours perfectly. During this period I made a few configurational changes. One of the last changes I made was to set email alerts. At some time later, it disappeared for several hours. Even after pushing the reset button it stayed missing for quite awhile longer before waking up on 192.168.0.32. Of course, I was switching back and forth between 192.168.4.x and 192.168.0.x looking for it. I should also say that during the entire missing period, the D-link discovery tool failed to show it although it worked fine prior to and following the missing period. It seems a real mystery to me. My private theory is that I somehow put the firmware into an infinite loop from which it eventually exited perhaps on pushing the reset button.

[fordem]

In the early days of my DNS-323 I was fooling around with ipsec VPNs and frequently moved it from one network to the other - using DHCP and DHCP reservations to make it easy to keep track of the device - it was always at .10 regardless of what the first three octets were.

It is possible to "lose" it if you're trying to access it by network name - this is actually a function of how Windows works and not a problem with the device, but it should always be accessible by ip address if you know what the address is.

Is there any possibility that you may had a network failure?  A bad cable or similar?

I believe your laptops are primarily wireless - perhaps, if there's a repeat occurence - you could try with laptop wired, just to eliminate the wireless from the equation.  I hasten to point out, that the only problems I have experienced using the device over wireless were all speed related, and again not specific to thedevice.

[sdhome]

Thanks fordem. All accesses were via the IP address ie, either 192.168.0.32 or 192.168.4.253. Also, the laptop was wired to router for all the tests although in the future I hope to access the drives wirelessly. As mentioned, the DNS-321 was hidden from Dlink discovery tool as well. I don't believe the cables were bad since they have not been changed and they worked fine before and after the disappearance. There have been no repeat occurrences. I am quite relieved that I can now reset to factory defaults if it should happen again.

I just received my Seagate drives and they have now been installed and formatted. I've begun to do some backups with SyncBackSE. So far everything is working fine.

[BillGalbraith]

I would also suggest updating it to the latest firmware revision.

Okay, you suggested that he update to the newest firmware. Where is it?

[jswashburn]

Okay, you suggested that he update to the newest firmware. Where is it?

Ya, sorry guys. My bad  I would have thought there might be one available. I even checked D-Links FTP site with no luck. 

[ECF]

There currently is no firmware update for the DNS-321.

[czhower]

My IP's are not in that range, but over UPNP the 321 always reports it is at 192.168.0.32 even though it is not.

[ECF]

192.168.0.32 is the default IP address of the DNS-321. It will revert to this IP address if an DHCP server is not present on the network.

[czhower]

I can see my 321 on its proper assigned DHCP IP, which is on a totally  different subnet. Yet UPNP still reports the default one.

[garyhgaryh]

There currently is no firmware update for the DNS-321.

What happened to 1.01? That's what I'm using and it's working great with my 1.5T seagate baracuda drives.
Gary

[ECF]

What happened to 1.01? That's what I'm using and it's working great with my 1.5T seagate baracuda drives.
Gary

Old post. That was from September 30 1.01 is now available

http://support.dlink.com/products/view.asp?productid=DNS-321