D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: e2000 on August 31, 2008, 07:30:10 PM
-
I have recently installed a new DNS-323 and upgraded its firmware to V1.05
The device works fine except of the web interface that stops responding from time to time - the browser can't connect to any page. At the same time the file system works fine and EasySearch finds the device.
The connectivity to the management web interface is restored only after manual power cycle.
I do not see any similar problem posted on this forum. Is there anything wrong in the configuration (please see the following config file)? Or I should replace the unit or flash it back to V1.04?
Thanks.
config file
----------------------
Version = v3.0
;CF-SYS-MODEL-STR = "NAS"
CF-WEB-IDLE-TIME = "10"
CF-IP-DHCP-ENABLE = "0"
CF-IP-STATIC-IP = "10.10.10.200"
CF-IP-STATIC-IP-NETMASK = "255.255.255.0"
CF-IP-STATIC-IP-GATEWAY = "10.10.10.1"
CF-IP-DNS1 = "208.67.222.222"
CF-IP-DNS2 = "208.67.220.220"
CF-TIMEZONE = "-4"
CF-METHOD = "1"
CF-WEB-USER-IDLE = "10"
CF-TIMESERVER = ""
CF-WL-WIRELESS = "0"
CF-WL-COMM-MODE = "2"
CF-WL-SSID = ""
CF-WL-CHANNEL = "0"
CF-WL-AUTH = "0"
CF-WL-SECURITY-MODE = "0"
CF-WL-ENCRYPTION-MODE = "0"
CF-WL-KEY-FORMATE = "0"
CF-WL-DEFAULT-KEY = ""
CF-WL-KEY-VALUE-1 = ""
CF-WL-KEY-VALUE-2 = ""
CF-WL-KEY-VALUE-3 = ""
CF-WL-KEY-VALUE-4 = ""
CF-WL-PSK = ""
CF-Daylight = "1"
CF-WL-MACADDRESS = ""
CF-WL-SIGNAL = ""
CF-WL-CONNECT = "0"
CF-WL-BEGIN-CHANNEL = "1"
CF-WL-END-CHANNEL = "11"
CF-WL-COUNTRY-REGION = "0"
CF-JUMBO = "0"
CF-WL-WIRELESS-MODE = "0"
CF-UDHCP = "0"
CF-QUOTA = "0"
CF-UDHCP-START-IP = "192.168.0.2"
CF-UDHCP-END-IP = "192.168.0.254"
CF-UDHCP-LEASE-TIME = "604800"
CF-POWER-MANAGE-STATE = "1"
CF-POWER-MANAGE-TIME = "5"
CF-iTunesServ = "0"
CF-LINKSPEED = "1000"
CF-UPNPAVServ = "0"
CF-COMPANY-URL = "http://www.dlink.com.tw/"
CF-UPNPAVPRESCAN = "i"
CF-LLTD = "0"
CF-JF-STATUS = "0"
CF-JF-MTU = ""
;ShareFolder:/mnt
;CF-AP-APStation = "1"
CF-AP-APOnOff = "0"
CF-AP-SSID = ""
CF-AP-CHANNEL = "0"
CF-AP-802-11G-ONLYMODE = "0"
CF-AP-SSID-BROADCAST = "0"
CF-AP-SECURITY-MODE = "0"
CF-AP-AUTH = "1"
CF-AP-ENCRYPTION-MODE = "1"
CF-AP-KEY-TYPE = "1"
CF-AP-DEFAULT-KEY = "1"
CF-AP-KEY-VALUE-1 = ""
CF-AP-KEY-VALUE-2 = ""
CF-AP-KEY-VALUE-3 = ""
CF-AP-KEY-VALUE-4 = ""
CF-AP-RADIUS-IP = ""
CF-AP-RADIUS-PORT = ""
CF-AP-RADIUS-SHARED-SECRET = ""
CF-AP-PSK = ""
CF-AP-SIGNAL = ""
CF-AP-TX-RATE = "0"
CF-AP-TRANSMIT-POWER = "0"
CF-AP-BEACON-INTERVAL = "100"
CF-AP-RTS-THRESHOLD = "2346"
CF-AP-FRAGMENTATION = "2346"
CF-AP-DTIM-INTERVAL = "1"
CF-AP-PREAMBLE-TYPE = "2"
CF-AP-CTS-MODE = "2"
CF-AP-OWN-IP-ADDRESS = "10.10.10.200"
CF-AP-SESSION-TIMEOUT-INTERVAL = "0"
CF-AP-PID = ""
CF-AP-AUTOCHANNEL = ""
;[ global ]
interfaces = egiga0
unix charset = UTF8
workgroup = workgroup
netbios name = NAS
server string = DNS-323 dlink-ABC1CF
hosts allow =
hosts deny =
security = SHARE
encrypt passwords = yes
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536
max xmit = 65535
create mask = 0777
directory mask = 0777
force create mode = 0777
force directory mode = 0777
load printers = Yes
printcap name = /usr/local/LPRng/etc/printcap
min print space = 2000
max print jobs = 1000
printing = lprng
print command = /usr/local/LPRng/bin/lpr -P%p -r %s
lpq command = /usr/local/LPRng/bin/lpq -P%p
lprm command = /usr/local/LPRng/bin/lprm -P%p %j
lppause command = /usr/local/LPRng/sbin/lpc hold %p %j
lpresume command = /usr/local/LPRng/sbin/lpc release %p %j
queuepause command = /usr/local/LPRng/sbin/lpc -P%p stop
queueresume command = /usr/local/LPRng/sbin/lpc -P%p start
use sendfile =yes
[ web_page ]
comment = Enter Our Web Page Setting
path = /mnt/web_page
valid users =
read only = yes
guest ok = yes
[printers]
path = /mnt/HD_a4/.lpd
guest ok = Yes
printable = Yes
use client driver = Yes
browseable = No
;0000
;admin:$1$$FJPyoONOplWjr8bPtadBh.:0:0:99999:7:::
nobody:pFCzI8gCXYNl3:0:0:99999:7:::
;nameserver 208.67.222.222
nameserver 208.67.220.220
;#!/bin/sh
/sbin/ifconfig egiga0 10.10.10.200 netmask 255.255.255.0
kill -9 `pidof udhcpc` 2>/dev/null
route del default
route add default gw 10.10.10.1
route add -net 224.0.0.0 netmask 255.0.0.0 dev egiga0
HOSTNAME='NAS'
echo "Setting hostname .... $HOSTNAME"
/bin/hostname $HOSTNAME
;root:x:0:0:Linux User,,,:/home/root:/bin/sh
admin:x:500:500:Linux User,,,:/home/admin:/bin/sh
nobody:x:501:501:Linux User,,,:/home/nobody:/bin/sh
;127.0.0.1 localhost.localdomain localhost
10.10.10.200 NAS NAS
;root:x:0:root
500:x:500:admin
501:x:501:nobody
;SADDR = ""
DADDR = ""
SERVER = ""
PORT = "25"
MODE = "0"
AUTH = "1"
UNAME = ""
PASSWD = ""
INTERVAL = "0"
TEMPERATURE = "140"
KOT = "F"
;CF-SYS-MODEL-STR = "DNS-323"
CF-WEB-IDLE-TIME = "10"
CF-IP-DHCP-ENABLE = "1"
CF-IP-STATIC-IP = "192.168.0.32"
CF-IP-STATIC-IP-NETMASK = "255.255.255.0"
CF-IP-STATIC-IP-GATEWAY = "192.168.0.1"
CF-IP-DNS1 = ""
CF-IP-DNS2 = ""
CF-TIMEZONE = "-8"
CF-METHOD = "2"
CF-WEB-USER-IDLE = "10"
CF-TIMESERVER = ""
CF-WL-WIRELESS = "0"
CF-WL-COMM-MODE = "2"
CF-WL-SSID = ""
CF-WL-CHANNEL = "0"
CF-WL-AUTH = "0"
CF-WL-SECURITY-MODE = "0"
CF-WL-ENCRYPTION-MODE = "0"
CF-WL-KEY-FORMATE = "0"
CF-WL-DEFAULT-KEY = ""
CF-WL-KEY-VALUE-1 = ""
CF-WL-KEY-VALUE-2 = ""
CF-WL-KEY-VALUE-3 = ""
CF-WL-KEY-VALUE-4 = ""
CF-WL-PSK = ""
CF-Daylight = "f"
CF-WL-MACADDRESS = ""
CF-WL-SIGNAL = ""
CF-WL-CONNECT = "0"
CF-WL-BEGIN-CHANNEL = "1"
CF-WL-END-CHANNEL = "11"
CF-WL-COUNTRY-REGION = "0"
CF-JUMBO = "0"
CF-WL-WIRELESS-MODE = "0"
CF-UDHCP = "0"
CF-QUOTA = "0"
CF-UDHCP-START-IP = "192.168.0.2"
CF-UDHCP-END-IP = "192.168.0.254"
CF-UDHCP-LEASE-TIME = "604800"
CF-POWER-MANAGE-STATE = "1"
CF-POWER-MANAGE-TIME = "5"
CF-iTunesServ = "1"
CF-LINKSPEED = "0"
CF-UPNPAVServ = "1"
CF-COMPANY-URL = "http://www.dlink.com.tw/"
CF-UPNPAVPRESCAN = "i"
CF-LLTD = "0"
CF-JF-STATUS = "0"
CF-JF-MTU = "1500"
;SYSTEM = "0"
EMAIL = "0"
;web_root /web
port 3689
admin_pw
db_dir /mnt/HD_a4/.systemfile/.mt-daapd
mp3_dir /mnt
tmp_dir /mnt/HD_a4/.systemfile
servername NAS
runas nobody
playlist /etc/mt-daapd.playlist
password
extensions .mp3,.m4a,.m4p
rescan_interval
;;0000
;#version = 1.06
[ Volume_1 ]
comment =
path = /mnt/HD_a2
valid users =
read only = no
guest ok = yes
oplocks = no
map archive = no
;#version = 1.06
[ Volume_2 ]
comment =
path = /mnt/HD_b2
valid users =
read only = no
guest ok = yes
oplocks = no
map archive = no
;kill -9 `pidof upnp`
/sys/custom/upnp/upnp 0 "D-Link Corporation" "http://www.dlink.com" "D-Link Network Storage Enclosure" "DNS-323" "103" &
;### Pure-ftpd configure ###
Version = "1.00"
Status = "stop"
MaxClientsNumber = "10"
MaxIdleTime = "2"
Port = "21"
FlowControl = "0"
FileSystemCharset = "UTF-8"
ClientCharset = "ISO8859-1"
;0000
;CF-DDNS-ENABLE = "0"
CF-DDNS-USERNAME = ""
CF-DDNS-PASSWORD = ""
CF-DDNS-DOMAIN = ""
CF-DDNS-SERVER = ""
CF-DDNS-TIMEOUT = "2073600"
;
-
Try accessing it from another PC on the network to see if maybe its your PC browser. If it fail still I would try a hard reset using the reset button on the back and reconfigure the unit. If you still see this problem I would say try reflashing the firmware. I don't think you need to go back to 1.04 nobody else has had this issue it seems 1.05 is fine.
-
It looks like the bittorent software has some play in that issue. Once I have it (bittorent) actively working, then the web interface stops responding. I tried accessing it from another PC with same result.
-
Odd..I have not herd of any other reports of this issue. Perhaps reflashing the firmware will solve this issue.
-
I'm also having that issue. I never used the tab much, but it worked fine previous to the 1.05 firmware (on 1.03). Now however, go figure the day I get an iPod and it becomes sorta useful, it's causing trouble.
I reloaded the 1.05 firmware with no luck. I'm gonna try going back to 1.04 to see if it mysteriously works.
Edit
No change after going to 1.04, going to 1.05 again. Will try a hard reset once more via the button on the back.
Edit
Hard refresh via the reset button on the back worked this time around. Wonder if iTunes will work any better now?
-
Same issues for me too, tried multiple browsers over multiple OS's, same deal. Also tried the reflashes, no dice. I'm at the point I'm ready to return my DNS-323 as this was the primary reason it was bought for.
-
Does it show the device on your network using the Easy Search Utility?
-
I too have this similar problem....
I'm on 1.05 was left my BT running overnight, next morning tried to access the 323 using the browser and the browser just hangs up (blank page - the logon page does not even come up). Tried access from another pc but also have the same problem. The 323 looked normal with the middle icon still blinking.
Funny thing is I was able to access the 323 mapped drives. was able to create & delete directories.
-
I know everyone is jumping on the BT client but there are other features that could cause this. Are any of you running iTunes server or UPNP AV server on your NAS? If so how much content do you have. If neither of you are running it and the device is strictly used for BT then I can understand however non of our devices have shown this kind of behavior in lab testing and the client goes through VERY strenuous testing to make sure it is unable to cause this.
Please any detailed information you can supply could help us reproduce this issue.
-
For my case I am only using the BT.
As for running iTunes server, i've tried ro DISABLE the iTunes server(disable and save the settings) but every time I log back on to the NAS, the iTunes sever is enable again.
And UPNP AV server on my NAS is enabled but have yet to pull any data from it yet...
-
This problem does not always happen.....
Been 2 days since the last reboot and am still able to logon
-
i have this same issue as well. interface just stops reponding
BT is in use (for the times it does crash)
iTunes server is disabled. i have tried to enable it, but when i do, it crashes again (i think my content is quite large for it to handle). so, no iTunes server for me
1.05
-
iTunes server is disabled. i have tried to enable it, but when i do, it crashes again (i think my content is quite large for it to handle). so, no iTunes server for me
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?
-
Ok, will disable the UPNP AV server...thanks for the advice
As for the how many active torrents and how heavy the BT usage at the time of the failure, I would not know as I cannot even logon to the 323. The only thing I know is, I was doing about 7 to 8 torrent at that time.
-
I still have that problem. You can see in the config printed in the original message that I have no iTunes, no UPNP, no jumbo frames or anything else enabled. The only possible reason could be BT or some general problem with the device. I don't believe I can troubleshoot it further without a telnet/ssh access to the device.
Just wanted to add that as other users already stated, the web interface connectivity problem does not affect other functionality of the device - when the web interface is down, I still can connect and use network drives of that device.
The telnet/ssh login that allows reset of the web server could provide a work-around for the problem.
I know everyone is jumping on the BT client but there are other features that could cause this. Are any of you running iTunes server or UPNP AV server on your NAS? If so how much content do you have. If neither of you are running it and the device is strictly used for BT then I can understand however non of our devices have shown this kind of behavior in lab testing and the client goes through VERY strenuous testing to make sure it is unable to cause this.
Please any detailed information you can supply could help us reproduce this issue.
-
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.
-
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?
-
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.
-
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.
-
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?
-
I have precisely same problem, whether but I have not understood there is a decision?
-
1.06 should be available very soon it looks. This I think will be the next step to resolving this issue at this point.
-
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
-
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.
-
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 :)