Hi,
just a little question for all the D-Link-users.
Has someone tried to install TwonkyMediaserver version 6 on den D-Link DNS 323?
Im still using 4.4.18 and would like to update to the newest build.
But version 5 didn`t run on my NAS.
Hopefully Twonky 6 does.
Grettings from Germany.
hagen
Twonky6 with D-Link DNS-323
-
- Posts:1
- Joined:Sun Jul 25, 2010 12:47 pm
- AV Hardware:DLINk DNS323
Re: Twonky6 with D-Link DNS-323
I have Twonky 6.0.1 successfully (I think) running on my DNS-323 now, once I corrected the amber/pink light issue.
Re: Twonky6 with D-Link DNS-323
I am looking at upgrading my Twonky software from 4.4.48 to 6.0.1. Since NAS's are no longer supported information is difficult to find. I already have the telnet setup on my DNS so that should not be an issue. Which download did you use for the version 6 Twonky on the DNS-323? What is the Amber/Pink light issue and how did you fix it? Were you able to use the installer (if it still comes with one) or did you install it manually?
Thanks.
Thanks.
Re: Twonky6 with D-Link DNS-323
The pink/amber light issue occurs upon startup of the DNS-323 after installing Twonky 6. I believe the memory in the root filesystem file in the NAS is used up and that prevents the NAS from fully booting and it will not be accessible from the network [see http://forum.dsmg600.info/viewtopic.php?id=5688]. To prevent it you need to edit the starttwonky.sh file [see http://forum.dsmg600.info/viewtopic.php?id=3726&p=1].
1. Download the DNS-323 Twonky NAS installation package at http://www.twonkyforum.com/downloads/6. ... -6.0.1.zip
2. Enable Telnet access on the NAS (already done in your case. http://wiki.dns323.info/howto:ffp
3. Run the DNS-323 Twonky NAS installer. Important - during installation uncheck the option box that will start the twonky server. If you forget to uncheck it, the server will start initiallizing after installation and you will get the pink/amber light issue.
4. Open the file starttwonky.sh in volume 1 of the NAS and change the contents to:
[code]
#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0
ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root
cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &
[/code]
Save the file. If I remember correctly, the only change to the code is the addition of the -appdata line.
5. Log on to telnet and start Twonky Server (with command /mnt/HD_a2/starttwonky.sh)
6. If you experience the pink/amber light issue already or forget to uncheck the start server box during the installation, it gets a little tricky. Using a PC (could not get it to work with my mac) there is a brief period during the boot/startup of the DNS-323 where you can access the NAS over your network before the twonky server starts to load. At this point the drive lights will still be clue. Quickly access the NAS and change the filename of starttwonky.sh in Volume 1 to something else (oldstarttwonky.sh or whatever), which will prevent twonky from loading and buy you some time to make other changes. Then open that file and make the above changes to it. Save the file and name it back to starttwonky.sh. Restart the DNS and it should work again. Remember, if you wait until the drive lights are pink to try accessing the NAS, it will not be visible on your network so you need to act fast while the lights are still blue during the boot for all of this to work.
Hope this longwinded post helps.
1. Download the DNS-323 Twonky NAS installation package at http://www.twonkyforum.com/downloads/6. ... -6.0.1.zip
2. Enable Telnet access on the NAS (already done in your case. http://wiki.dns323.info/howto:ffp
3. Run the DNS-323 Twonky NAS installer. Important - during installation uncheck the option box that will start the twonky server. If you forget to uncheck it, the server will start initiallizing after installation and you will get the pink/amber light issue.
4. Open the file starttwonky.sh in volume 1 of the NAS and change the contents to:
[code]
#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0
ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root
cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &
[/code]
Save the file. If I remember correctly, the only change to the code is the addition of the -appdata line.
5. Log on to telnet and start Twonky Server (with command /mnt/HD_a2/starttwonky.sh)
6. If you experience the pink/amber light issue already or forget to uncheck the start server box during the installation, it gets a little tricky. Using a PC (could not get it to work with my mac) there is a brief period during the boot/startup of the DNS-323 where you can access the NAS over your network before the twonky server starts to load. At this point the drive lights will still be clue. Quickly access the NAS and change the filename of starttwonky.sh in Volume 1 to something else (oldstarttwonky.sh or whatever), which will prevent twonky from loading and buy you some time to make other changes. Then open that file and make the above changes to it. Save the file and name it back to starttwonky.sh. Restart the DNS and it should work again. Remember, if you wait until the drive lights are pink to try accessing the NAS, it will not be visible on your network so you need to act fast while the lights are still blue during the boot for all of this to work.
Hope this longwinded post helps.
-
- Posts:9
- Joined:Wed Oct 20, 2010 11:54 pm
- AV Hardware:dns0323, ps3
Re: Twonky6 with D-Link DNS-323
I just tried to install Twonky 6.x today on my dsn-323. I forgot to uncheck start server option. So it finished successfully and restarted server. No pink light but I can not access drive anymore. I can user webbrower only to access it. How can I resolve this issue now. If I format my drive, will it fix the issue? I already restored dsn-323 to factory default.
-
- Posts:9
- Joined:Wed Oct 20, 2010 11:54 pm
- AV Hardware:dns0323, ps3
Re: Twonky6 with D-Link DNS-323
docmbs's instructions work very well. Thanks.