Print

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

[EtownOilFan]

I'm having this issue as well. The NAS is functioning just fine. Everything is accessible with the exception of the web interface (and the vista gadget). I can ping the IP and it's responsive, but it loads up blank.

I have not enable BT, but I am using the media server and the itunes server.

I've tried using the reset on the back and no change.

[EtownOilFan]

I had restarted my router recently when my ISP was down over night, and messed up my connection. I ran the easy search utility again, and found the NAS IP had changed from...

192.168.1.100

to

192.168.1.101

So, it's actually working fine now. Is there a way to avoid this in the future?

[fordem]

EtownOilFan - you can either set a static ip address in the DNS-323 LAN configuration - or - you can reserve an address for it using the DHCP server - presumably in your router.

e2000 - I notice that you have been perhaps editing your config file or at least looking at it.  I believe there is what can be considered a known problem where opening/editing the config file with a Windows based editor can cause the file to become corrupted and restoring the corrupt file to the device will cause the internal web server to hang.

If I remember correctly it has something to do with CR+LF - carriage return and line feed - which are apparently handled differently by the two operating systems.

[e2000]

Hi fordem,
I have edited my config file to scramble authentication info before it is uploaded to the web. I have not uploaded that modified config into DNS-323.

Interesting enough that the web interface problem does not happen for a while now... I do not think I changed any option (except of the BT settings) though.

e2000 - I notice that you have been perhaps editing your config file or at least looking at it.  I believe there is what can be considered a known problem where opening/editing the config file with a Windows based editor can cause the file to become corrupted and restoring the corrupt file to the device will cause the internal web server to hang.

If I remember correctly it has something to do with CR+LF - carriage return and line feed - which are apparently handled differently by the two operating systems.

[Pattmyn]

Does it show the device on your network using the Easy Search Utility?

Sorry for the ages between replies. Yes it's visible in easy search, the drive is still network mountable and accessible but the web interface is pooched. I have absolutely every setting/server turned off on the unit as I primarily run it as a NAS and Torrent box. The other mod mentioned a possible fix for this crashing issue in 1.06? Any ETA on that and/or confirmation of it being an issue?

[KAmerad]

I have precisely same problem, whether but I have not understood there is a decision?

[ECF]

1.06 should be available very soon it looks. This I think will be the next step to resolving this issue at this point.

[espiritu]

seems to be related to large torrents...as i dont have any problems with having many torrents active, but when i have the large torrent/torrents active the web interface stops responding.

i have the itunes server, and the Upnp disabled but i have LLTD enabled.

as reported above, the drives remain mounted and active even the torrent appears to continue.

i have tried multiple machines/browsers

I am running the with 2 x 1.5tb drives as separate volumes with firmware v1.05

[perradise]

This issue should go away next firmware. It is really hard to say what is causing the web server to fail.

Fireball,

If you are not using the UPNP AV server I would suggest disabling it since it uses up device resources even if it is just enabled. When your interface stops responding is this also after heavy BT usage? How many torrents would you say are in Queue at time of failure? How many active?

If "it is really hard to say what is causing the web server to fail", then what makes you so confident that is will go away with the next firmware?  I'm using firmware v1.09 and am still experiencing this problem.

[dosborne]

It has been determined that the BT app causes the admin console to 'die' after a period of time. This has been discussed in threads less than 2 years old