DSM-G600, DNS-3xx and NSA-220 Hack Forum

lucianf · 2009-08-05 03:41:34

Help please

Hi, I've just purchased a DNS-323 and cannot connect to it.

I have two Hitachi 0A38016 (7K1000.B - 1 TB each). I know they are not supposed to work unless the latest firmware is employed (and I can't check what firmware my unit came with - as I cannot access the web interface), but I'd still expect to be able to access the unit through web.

Most of the times I start the unit it will keep flashing the power light and no ip will be assigned (also connecting to the default 192.168.0.32 doesn't work). A few times (apparently doing nothing special - just rebooting forcefully, i.e. by unplugging the unit from the socket - as the power button would not work while blinking) I managed to get the power light to turn solid blue. Then the unit was assigned an IP (DHCP) but that IP only replies to ping - connecting from a web browser doesn't work (I also ran nmap and all ports between 1-1024 came as closed).

Also, the Easy Search Utility never manages to display the unit (refresh doesn't show anything). I hope this is enough technical information to get you started, but if you need anything else let me know, I'm very proficient in IT/hardware.

Is this a brand new brick?

Thanks, Lucian

Edit: It's rev B1 with firmware 1.07 as I found on the bottom label.. also, tried with a 3rd hdd (a Maxtor 320 GB) - same thing, can ping but can't connect on web (telnet to port 80 doesn't work either). And I'm not using any software for blocking such connections.

Last edited by lucianf (2009-08-05 03:58:41)

HooKy · 2009-08-05 07:25:43

What OS R U running? Windows 7 perhaps?

If so, then the problem is likely Win7 related... I am having all kinds of trouble getting Win7 to recognize my DNS-323. I have been through all the fixes (all I can find here & elsewhere anyways) and none of them seem to work on any of my Win7 machines - I do get variable errors depending on the machine and the build, but one of my Win7 machines behaves exactly as you describe - like the DNS-323 box was not even there (even thought I can ping it from said machine).

All the while my Vista/Server/OSX machines have no problem seeing the DNS-323 and all of its shares.

(I posted this only to let you know you may not have a brick - not because I have a solution... at least not yet.)

H-

lucianf · 2009-08-05 13:21:49

Thanks. I'm on Mac OS X, but I've also tried connecting from an XP Pro virtual machine, so I'm pretty sure it's got nothing to do with the OS...

fordem · 2009-08-05 14:54:09

I think it's time to call tech support and get it replaced.

In my experience a flashing power light indicates it's so to speak booting up, and if the light continues to flash for more than 3~4 minutes, it's indicative of a problem of some sort - normal boot on my unit takes about 80 seconds, this can vary depending on how long the drives installed take to "come ready".

There are a couple of potential problems that can cause it not to boot, bad drives, corrupt configuration files - but you've tried different drives and on a new unit you shouldn't have configuration file issues.

One last thing - out of box there is no telnet server, http is the only thing that should be running.

lucianf · 2009-08-06 00:29:37

Thanks. That's what I'm afraid of too. So there is absolutely no reason for 1) the power light to stay blinking for as long as 30 minutes, and 2) the device to not accept connections to port 80 (www) even if it acquired an IP (DHCP or the 0.32 default one)? Again, the device is brand new, and I never managed to connect to it (hence no mods/config changes were ever attempted).

spider · 2009-08-30 07:38:54

I had the exact same issue with a brand new unit from Amazon. It shipped with firmware 1.04 - you need 1.07 to support the larger drives. Find out the IP of the device (look at DHCP leases on your router) or use nmap - it should be listening on 80 and 443.

Login with default admin, update firmware, and you should be good to go.

spider · 2009-08-30 08:17:21

PS I ended up on this thread because I kept getting the dreaded "The operation can’t be completed because the original item for Volume_1 can’t be found" when trying to connect to the DNS from Windows and Mac. The solution seems to be a 1.8 beta (at this writing) firmware upgrade to the DNS. Thanks to this macrumors thread for the tip

Links to download the beta firmware can be found at http://forums.dlink.com/index.php?board=251.0

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1 2009-08-05 03:41:34

New unit - cannot connect

#2 2009-08-05 07:25:43

Re: New unit - cannot connect

#3 2009-08-05 13:21:49

Re: New unit - cannot connect

#4 2009-08-05 14:54:09

Re: New unit - cannot connect

#5 2009-08-06 00:29:37

Re: New unit - cannot connect

#6 2009-08-30 07:38:54

Re: New unit - cannot connect

#7 2009-08-30 08:17:21

Re: New unit - cannot connect

Board footer