Differences
This shows you the differences between the selected revision and the current version of the page.
| information:known_issues 2010/07/18 01:10 | information:known_issues 2022/03/11 12:02 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Known Issues ====== | + | ====== Known Issues ====== |
| Unfortunately, the DNS-323 isn't a perfect piece of equipment. | Unfortunately, the DNS-323 isn't a perfect piece of equipment. | ||
| It contains a bunch of [[wp>Software_bug|bugs]] and some compatibility issues. | It contains a bunch of [[wp>Software_bug|bugs]] and some compatibility issues. | ||
| Line 11: | Line 11: | ||
| newer firmware revisions: | newer firmware revisions: | ||
| + | * FW 1.10.0, provide some fix and Advanced Disk architecture which is mandatory for new large disks | ||
| + | * FW 1.0.9, dated 06/16/2010, described [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_release_notes.txt|here]] and located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_fw_109.zip|here]] | ||
| + | * FW 1.0.8, dated 02/17/2010, located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_firmware_108.zip|here]] | ||
| * FW 1.0.7, dated 03/27/2009 and 2009-04-16, located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/|here]] | * FW 1.0.7, dated 03/27/2009 and 2009-04-16, located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/|here]] | ||
| * FW 1.0.6, released 2008-12-29, described [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_release_notes_106.txt|here]] and available [[http://support.dlink.com/products/view.asp?productid=DNS-323#apps|here]]. | * FW 1.0.6, released 2008-12-29, described [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_release_notes_106.txt|here]] and available [[http://support.dlink.com/products/view.asp?productid=DNS-323#apps|here]]. | ||
| Line 16: | Line 19: | ||
| Note that the web screens for the DNS-323 may show the firmware as "1.07" | Note that the web screens for the DNS-323 may show the firmware as "1.07" | ||
| not "1.0.7". | not "1.0.7". | ||
| + | |||
| + | |||
| + | |||
| ===== Adding an extra disc can wipe both! ===== | ===== Adding an extra disc can wipe both! ===== | ||
| + | //Firmware//: 1.09\\ Appears to have resolved this issue. Starting with a single disk in the LEFT bay, I was able to add a second matched blank disk to the right bay. After rebooting I selected RAID1 with manual rebuild and then manual rebuild. (Sorry didn't keep the exact procedure, but I did a couple of disk changes and it seemed to work correctly every time.) | ||
| + | |||
| //Firmware//: 1.05\\ | //Firmware//: 1.05\\ | ||
| //Severity//: High\\ | //Severity//: High\\ | ||
| Line 33: | Line 41: | ||
| the one listed in the RAID menu. | the one listed in the RAID menu. | ||
| Perhaps this 'bug' is due to not following directions in the manual? | Perhaps this 'bug' is due to not following directions in the manual? | ||
| - | |||
| ===== Adding an extra disc can wipe data on existing drive! ===== | ===== Adding an extra disc can wipe data on existing drive! ===== | ||
| - | //Firmware//: 1.03, 1.05, 1.06, 1.07 are all confirmed\\ | + | //Firmware//: 1.03, 1.05, 1.06, 1.07, 1.08 are all confirmed\\ |
| //Severity//: High\\ | //Severity//: High\\ | ||
| //Description//: Consider you have one disk installed in the right hand bay, when looking at the front cover of the DNS-323. Now insert a second drive in the left bay while the device is powered off. After powering up the web interface will prompt "Your new, second hard drive will now be formatted. The existing harddrive will not lose any data." It will display the vendor/model/serial number and size of the second drive. However if you press "next" it will format the first disk in the right bay.\\ | //Description//: Consider you have one disk installed in the right hand bay, when looking at the front cover of the DNS-323. Now insert a second drive in the left bay while the device is powered off. After powering up the web interface will prompt "Your new, second hard drive will now be formatted. The existing harddrive will not lose any data." It will display the vendor/model/serial number and size of the second drive. However if you press "next" it will format the first disk in the right bay.\\ | ||
| //Remarks//: Slight variations to this procedure might not result in this bug. For example starting with the first drive being installed in another bay or hot adding (= while being powered on) drives.\\ | //Remarks//: Slight variations to this procedure might not result in this bug. For example starting with the first drive being installed in another bay or hot adding (= while being powered on) drives.\\ | ||
| //Workaround//: Don't have other disks installed when formating a new drive. Boot bay with just the new drive installed, format, power off, reinstall first disk afterwards. If volume numbering and network shares mess up, you can still swap drives. Or search forum for manually formating drives\\ | //Workaround//: Don't have other disks installed when formating a new drive. Boot bay with just the new drive installed, format, power off, reinstall first disk afterwards. If volume numbering and network shares mess up, you can still swap drives. Or search forum for manually formating drives\\ | ||
| - | //Links//:http://forum.dsmg600.info/t3113-Arghhh.-Drive-wiped.html\\ | + | //Links//:http://dns323.kood.org/forum/t3113-Arghhh.-Drive-wiped.html\\ |
| - | http://forum.dsmg600.info/t885-OMFG%2C-Lost-data!-D-link-terrible!.html | + | http://dns323.kood.org/forum/t885-OMFG%2C-Lost-data!-D-link-terrible!.html |
| //Note for FW 1.0.4//:\\ | //Note for FW 1.0.4//:\\ | ||
| Line 55: | Line 62: | ||
| Perhaps this 'bug' is due to not following directions in the manual? | Perhaps this 'bug' is due to not following directions in the manual? | ||
| + | //How to avoid this//:\\ | ||
| + | Remember to insert the first HDD into the left handside bay (what is said in the manual). The left one is always the first one, the right one (if exists) is always the second one. If it were to format "the second drive", it is the one on the right handside. | ||
| ===== Adding a disk causes FFP to stop working ===== | ===== Adding a disk causes FFP to stop working ===== | ||
| Line 99: | Line 107: | ||
| the right slot and fun_plug stops working until you swap the disks. | the right slot and fun_plug stops working until you swap the disks. | ||
| - | ===== Windows Vista Can't Access Shares After A While ===== | + | |
| - | //Firmware//: 1.05\\ | + | ===== Windows Vista and Windows 7 Can't Access Shares After A While ===== |
| + | //Firmware//: 1.05,1.09,1.10\\ | ||
| //Severity//: High\\ | //Severity//: High\\ | ||
| - | //Description//: After some period of normal usage, shares on the DNS-323 can no longer be accessed by Windows Vista.\\ | + | //Description//: After some period of normal usage, shares on the DNS-323 can no longer be accessed by Windows Vista or Windows 7.\\ |
| //Workaround//: Files can be recovered by connecting via FTP, or from a non-Vista computer.\\ | //Workaround//: Files can be recovered by connecting via FTP, or from a non-Vista computer.\\ | ||
| - | //Fix//: Disable Flow Control, IP Checksum Offload, Priority & VLAN, TCP and UDP Checksum Offloads if your network adapter has these options and you should be able to access the DNS-323. This is based off a Nvidia based chipset. Options will differ per board or card.\\ | + | |
| + | //Fix//: Disable Flow Control, IP Checksum Offload, Priority & VLAN, TCP and UDP Checksum Offloads if your network adapter has these options and you should be able to access the DNS-323. This is based off a Nvidia based chipset. Options will differ per board or card. \\ | ||
| + | Also make sure the following entry exists in the C:\Windows\System32\drivers\etc\hosts file (and remember to reboot both the device and the Windows machine after making the changes). For eg. if your DNS-323 device IP is 194.164.92.101\\ | ||
| + | 194.164.92.101 dns-323\\ | ||
| //Fix//:If you still can connect to the DNS-323 configuration through web browser go to "Advanced/Network Access Settings" and try to give all accounts access to the shared folder | //Fix//:If you still can connect to the DNS-323 configuration through web browser go to "Advanced/Network Access Settings" and try to give all accounts access to the shared folder | ||
| Line 249: | Line 262: | ||
| //Description//: Users with Windows 2003 and Windows Vista has reported that they fail to transfer 'large' files to the unit. Some reports indicates that this is not an issue with Windows XP. Apparently files in the range 2-4Gb, 6-8Gb and 10-12Gb fails to transfer while 0-2Gb, 4-6Gb, 8-10Gb and 12-14Gb transfers ok. | //Description//: Users with Windows 2003 and Windows Vista has reported that they fail to transfer 'large' files to the unit. Some reports indicates that this is not an issue with Windows XP. Apparently files in the range 2-4Gb, 6-8Gb and 10-12Gb fails to transfer while 0-2Gb, 4-6Gb, 8-10Gb and 12-14Gb transfers ok. | ||
| - | According to findings by [[http://forum.dsmg600.info/profile.php?id=209|tobyg]], as [[http://forum.dsmg600.info/p1419-Yesterday-095533.html#p1419|posted]] on our forum, the problem is a signing issue in the 2.x.x branch of Samba. Or to put it as [[http://forum.dsmg600.info/profile.php?id=209|tobyg]] says: | + | According to findings by [[http://dns323.kood.org/forum/profile.php?id=209|tobyg]], as [[http://dns323.kood.org/forum/p1419-Yesterday-095533.html#p1419|posted]] on our forum, the problem is a signing issue in the 2.x.x branch of Samba. Or to put it as [[http://dns323.kood.org/forum/profile.php?id=209|tobyg]] says: |
| >So go into byteorder.h and change this line: | >So go into byteorder.h and change this line: | ||
| Line 257: | Line 270: | ||
| >''#define CVAL(buf,pos) ( (unsigned)( ( (const unsigned char *)(buf))[pos]))'' | >''#define CVAL(buf,pos) ( (unsigned)( ( (const unsigned char *)(buf))[pos]))'' | ||
| \\ | \\ | ||
| - | //Workaround//: The Samba daemon needs to be replaced. [[http://forum.dsmg600.info/profile.php?id=209|tobyg]] has submitted patched files and a script, which can be used at **own risk**. Instructions and the files needed can be found in this [[http://forum.dsmg600.info/p1419-Yesterday-095533.html#p1419|thread]]. | + | //Workaround//: The Samba daemon needs to be replaced. [[http://dns323.kood.org/forum/profile.php?id=209|tobyg]] has submitted patched files and a script, which can be used at **own risk**. Instructions and the files needed can be found in this [[http://dns323.kood.org/forum/p1419-Yesterday-095533.html#p1419|thread]]. |
| //Mounting from Linux//: Many linux distros will not mount smb default with Large file support. Use the mount -o lfs option to get Large file support. | //Mounting from Linux//: Many linux distros will not mount smb default with Large file support. Use the mount -o lfs option to get Large file support. | ||
| - | [[http://forum.dsmg600.info/t491-Large-files.html|thread]] | + | [[http://dns323.kood.org/forum/t491-Large-files.html|thread]] |
| Line 311: | Line 325: | ||
| **__Update: 05-Sept-07;__ | **__Update: 05-Sept-07;__ | ||
| Same problem for my network (cannot accès the DNS, no disk mapped). I fix one static IP for my DNS-323 (192.168.1.99) and all works fine !!!!!! | Same problem for my network (cannot accès the DNS, no disk mapped). I fix one static IP for my DNS-323 (192.168.1.99) and all works fine !!!!!! | ||
| + | \\ | ||
| **__Update: 11-Jun-10;__ | **__Update: 11-Jun-10;__ | ||
| After the DNS was booted it is not possible to access any network shares by using device name(dns323) but ip address can, to slove this i need to telnet the device | After the DNS was booted it is not possible to access any network shares by using device name(dns323) but ip address can, to slove this i need to telnet the device | ||
| Line 318: | Line 332: | ||
| question : any better solution? | question : any better solution? | ||
| \\ | \\ | ||
| + | **__Update: 15-Sep-2011;__** | ||
| + | With firmware 1.09 I still have occasionally come across this bug. Before reading about this issue here I was unable to find the real reason, but fiddling with the access right in the NETWORK ACCESS section did it. It would be helpful to clean this bug description from workarounds that deal with other machines (e.g. dns323 alias in the /etc/hosts-file). | ||
| + | \\ | ||
| + | **__Update: 01-Aug-2012;__** | ||
| + | Bug was still there after the last swapping of drives, so when trying to mount I got:\\ | ||
| + | // | ||
| + | prompt:~$ sudo mount -a\\ | ||
| + | retrying with upper case share name\\ | ||
| + | mount error(6): No such device or address\\ | ||
| + | Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)\\ | ||
| + | // | ||
| + | |||
| + | This time fiddling with the NETWORK ACCESS LIST did not work. I was only able to re-establish access if I deleted the network access list completely (i.e. pressed the button "Reset Network Access List"). This is a pain because then I had to redo all the shares. | ||
| + | \\ | ||
| + | |||
| Thx for this issue. | Thx for this issue. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| ===== UPnP AV Server issues ===== | ===== UPnP AV Server issues ===== | ||
| Line 334: | Line 370: | ||
| UPnPAV: all of the data wasn't sent, so queue this up.(ILibAyincSocket_Send)\\ | UPnPAV: all of the data wasn't sent, so queue this up.(ILibAyincSocket_Send)\\ | ||
| //Workaround//: Disable onboard upnpav and install Twonkyvision?\\ | //Workaround//: Disable onboard upnpav and install Twonkyvision?\\ | ||
| - | |||
| - | |||
| - | |||
| - | |||
| ===== Email Alerts ===== | ===== Email Alerts ===== | ||
| Line 350: | Line 382: | ||
| + | **Email account passwords cannot contain certain characters (e.g. semi-colon):** When the email application is invoked, your email account password is **not** properly escaped for [[http://en.wikipedia.org/wiki/Almquist_shell|ash]], causing certain characters of your password to be interpreted (e.g. a semi-colon is interpreted as the end of the current command execution). Thus, having a password of ";poweroff" could prove quite frustrating. LOL | ||
| + | Bug reported to D-Link on Aug 31, 2010 under case #ALR401034497 (unresolved as of firmware 1.09). | ||
| ===== Zone Alarm ===== | ===== Zone Alarm ===== | ||
| Line 399: | Line 432: | ||
| //D-Link correction//: N/A\\ | //D-Link correction//: N/A\\ | ||
| //Description//: The Dynamic DNS (DDNS) feature used to update your dynamic IP and host a server, doesn't behave correctly. After a few hours, you will get blocked from www.dyndns.org and get a notice: Hostname Blocked Due To Abuse.\\ | //Description//: The Dynamic DNS (DDNS) feature used to update your dynamic IP and host a server, doesn't behave correctly. After a few hours, you will get blocked from www.dyndns.org and get a notice: Hostname Blocked Due To Abuse.\\ | ||
| - | //Workaround//: Look at this thread: http://forum.dsmg600.info/p15441-2008-05-23-06:16:22.html | + | //Workaround//: Look at this thread: http://dns323.kood.org/forum/p15441-2008-05-23-06:16:22.html |
| ===== Problem loading Libraries and Executables Issue ===== | ===== Problem loading Libraries and Executables Issue ===== | ||
