D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-343 => Topic started by: JavaLawyer on June 18, 2012, 11:07:05 AM
-
The latest DNS-343 beta firmware, version 1.06b01 is posted here: DNS-343 - Beta Firmware 1.06 Build 01 (http://forums.dlink.com/index.php?topic=49246.0).
No release notes accompanied this release.
Please post your comments and observations on this thread. ;)
-
I put some feelers out to find out what changed in this latest version. ??? ??? ???
-
It adds Passive port configuration to the FTP server.
-
Thanks Lycan.
-
Fingers crossed for improved NFS performance. Though I don't have the nerve to be an early beta tester... especially without a changelog.
-
. . . I don't have the nerve to be an early beta tester... especially without a changelog.
Lycan's word is as good as a changelog. He works for D-Link and has ties to the development team.
The lack of a changelog/release notes is simply an oversight.
-
I like living dangerously so I took the plunge. What is passive port configuration by the way?
-
I like living dangerously so I took the plunge. What is passive port configuration by the way?
Active vs. Passive FTP
In active FTP, which was designed before firewalls were common, Fetch tells the server "this is the port you should talk to me on," and the server attempts to connect to that port. This is like Fetch giving the server a phone number to call your computer at. The firewall blocks incoming calls, so you get an error when trying to open a connection because Fetch never hears from the server.
In passive FTP, Fetch asks the server to pick a port, and then connects to the server on that port. This is like Fetch asking at what phone number it can call the server. Since Fetch makes the call, the firewall allows it, and you are all set to transfer files.
-
Thanks for the explanation JavaLawyer. Are there advantages (i.e. security) of one over the other?
-
From my understanding, the inherent risk associated with FTP in general due to the insecure login protocol (vs. secure FTP), trump any new risk introduced by passive vs. active mode. Passive does provide the benefit of allowing access that may otherwise be blocked by a firewall.
-
Ah. Thanks. That answers my question. Are there plans to implement SFTP on the DNS-343? That would be awesome. Is my understanding correct when I say that not using SFTP and instead allowing regular FTP connections is not secure because username and password information and sent across the internet in the clear and unencrypted?
-
Thanks for the 1.06
It fixed the System Halt issue that I had from the Power button on the Unit and from the GUI
Now Im able to shutdown the unit.
Thanks
-
Thanks for the 1.06
It fixed the System Halt issue that I had from the Power button on the Unit and from the GUI
Now Im able to shutdown the unit.
Thanks
That's good news. I haven't performed a soft shutdown since upgrading my DNS-343s to firmware v1.06b01.
-
Just realized that I cannot change DEVICE name with 1.06.
I get a error in IE:
Internet Explorer cannot display the webpage
http://10.10.1.105/goform/CfgGlobal
Anyone else with the same issue??
-
What version of IE? If 8 or 9, try compatibility mode? Does this happen with other browsers like Opera or FF?
Just realized that I cannot change DEVICE name with 1.06.
I get a error in IE:
Internet Explorer cannot display the webpage
http://10.10.1.105/goform/CfgGlobal
Anyone else with the same issue??
-
It happens on IE9 / Chrome / FireFox
Same issue in compatibility mode.
-
Just realized that I cannot change DEVICE name with 1.06.
I get a error in IE:
Internet Explorer cannot display the webpage
http://10.10.1.105/goform/CfgGlobal
Anyone else with the same issue??
Are you referring to the field located on the web UI at SETUP > Device > Device Settings > Name?
-
Are you referring to the field located on the web UI at SETUP > Device > Device Settings > Name?
YES... In fact Both Name and Description fields.
-
Did you ever change the device name using FW version 1.05? The only difference between v1.05 and v1.06 is FTP handling.
-
Yes I did!
on version 1.05 I was also unable to shutdown my DNS-343
-
Yes I did!
on version 1.05 I was also unable to shutdown my DNS-343
Looks like I have some testing to do. . .
-
Another thing I discovered today.
Shutdown via GUI in 1.06 = WORKS
Shutdown via POWER button in 1.06 = System Halts Issue
-
Another thing I discovered today.
Shutdown via GUI in 1.06 = WORKS
Shutdown via POWER button in 1.06 = System Halts Issue
I can validate that shutdown via GUI in v1.06 works, but have not tested the power button (yet).
-
Any news on the bugs? Is there a fix? A new beta version?
thanks
-
Any news on the bugs? Is there a fix? A new beta version?
thanks
No news on any bug fixes or forthcoming firmware updates.
-
Since November.... Any news on any possible fix on 1.06 Beta2 build release or a 1.07 release?
Thanks
-
Haven't heard anything new. :-\
-
Since November.... Any news on any possible fix on 1.06 Beta2 build release or a 1.07 release?
Thanks
"...fix on 1.06 Beta2 build release..." Has there been a build 2 release of beta version 1.06?
-
The latest DNS-343 firmware release is version 1.06b01.
-
I had to redo a full reset of my DNS-343. I was lucky that I had a full backup of it.
Now my big issue, because of 1.06 Firmware Im not able to change the Name of it
in the Device Settings. Everything else can be changed. But the name stays with the
random dlink name: dlink-14B096
Is it possible to rollback to 1.05. So I could change the device name...
Then upgrade to 1.06 again?
Or any plan to fix this issue? or any other way to change the device name??
-
I had to redo a full reset of my DNS-343. I was lucky that I had a full backup of it.
Now my big issue, because of 1.06 Firmware Im not able to change the Name of it
in the Device Settings. Everything else can be changed. But the name stays with the
random dlink name: dlink-14B096
Is it possible to rollback to 1.05. So I could change the device name...
Then upgrade to 1.06 again?
Or any plan to fix this issue? or any other way to change the device name??
You should be able to roll back to firmware v1.05 without issue and migrate back to v1.06. I don't know if v1.05 supports device name changes -- the names on my two DNS-343 were established in v1.04, and I haven't tried changing them since.
-
Just did it... And 1.05 Supports Device Name change without any issue.
So Now im back to 1.06 Beta and Im about to restore my backup to it.
I was just afraid to create corruption by rolling back to 1.05 and then again to 1.06
Thanks
-
I'm glad everything worked out. The only published change from v1.05 to 1.06 was related to FTP, nothing that would impact HDD configuration.
-
It worked yes.... But now I have some issues!!!
My slot1 is telling giving me a HDD status of Abnormal and my RAID is Degraded....
Lucky I have 2 other 2GB drives available.... But It did teh same for bith of them....
Something is wrong!!!! Could it be the Slot1 or the 1.06 Beta that is not working as designed??
Im planning on rolling back to 1.05 and Reset + Factory Default everything and restart my backup copy Again!
-
It's possible that a HDD is failing, as that would cause the Degraded message. You can go back to v1.05 and see if the message goes away. Rolling back shouldn't impact anything.
-
3 HDD failing! 2 brand new... and 1 that I was using just before without any errors.... I find it strange!
-
3 HDD failing! 2 brand new... and 1 that I was using just before without any errors.... I find it strange!
Yes, odd. Changing the FW should have no impact on HDD configuration, especially a release as insubstantial as 1.06, which only touched on FTP.
-
Any update on this issue?
-
Did a full reset.... seems to be ok and stable now... But on FW 1.05.
Was able to copy 100GB to it without any issue.
Redid a full reset... Upgraded to FW1.06B
While trying to copy the same 100GB the copy stopped and I had an error on Slot1
Something is fishy with FW1.06B!
Redid a full reset... Downgraded to FW1.05
Copied the same 100GB with success.
DNS-343 stable for the last 8hours
-
Thanks for your feedback. This begs the question as to whether v1.06b01 has some underlying changes that impacts RAID. My DNS-343s are configured as Standard Volumes, and I haven't had any issues. :-\
-
i have a DNS-343 firmware r1.0. It has 4 2TB HDD installed and they are almost full of data. I don't have any backups of this data. i want to upgrade my firmware to r1.05. i am concerned about issues with the hard drives wanting to reformat after an upgrade. My question is can i safely upgrade my firmware from r1.0 -> r1.05 with HDDs installed without compatibility issues or the software wanting to reformat my HDDs. I should add that these drives are arranged as JBOD and accessed via Windows XP.
Thanks !
-
i have a DNS-343 firmware r1.0. It has 4 2TB HDD installed and they are almost full of data. I don't have any backups of this data. i want to upgrade my firmware to r1.05. i am concerned about issues with the hard drives wanting to reformat after an upgrade. My question is can i safely upgrade my firmware from r1.0 -> r1.05 with HDDs installed without compatibility issues or the software wanting to reformat my HDDs. I should add that these drives are arranged as JBOD and accessed via Windows XP.
Thanks !
Firmware version 1.0? Really? I can say from personal experience that migrating firmware version 1.03 and onward should not impact existing stored data or HDD configuration (e.g. v1.03 to v1.04 or v1.04 to 1.05). I've never dealt with (or read about) user experiences upgrading from version 1.0. You may want to try an incremental approach (e.g. 1.0 > 2.0; 2.0 > 3.0; etc).
Regardless of your approach, I can't stress how important it is for you to backup your data before performing any migration, especially from an older firmware version. Please read the following thread DNS-343 - Data Backup vs. Redundancy (http://forums.dlink.com/index.php?topic=46512.0)
-
my mistake...it's actually v1.01
I purchased it new in '09 , installed 4 seagate 2TB drives, and it has run flawless since. i never even thought about firmware upgrades until recently. i think i will just let sleeping dogs lay.
:-)
Thanks for the info!
-
my mistake...it's actually v1.01
I purchased it new in '09 , installed 4 seagate 2TB drives, and it has run flawless since. i never even thought about firmware upgrades until recently. i think i will just let sleeping dogs lay.
:-)
Thanks for the info!
If it's not broken, don't fix it ;)
If your data is important to you, make a backup as soon as possible. There's no recovery from a hard drive failure.
-
Oh i forgot to ask you. In the event that i do attempt to upgrade in the future, where can i d/l a copy of v1.01 firmware so i can rollback versions if need be. I didn't see anything that old on the D-Link site. Oldest version i seen was v1.02
Thanks again!
-
Oh i forgot to ask you. In the event that i do attempt to upgrade in the future, where can i d/l a copy of v1.01 firmware so i can rollback versions if need be. I didn't see anything that old on the D-Link site. Oldest version i seen was v1.02
Thanks again!
You will find all prior DNS-343 firmware releases here; D-Link Taiwan Site (Downloads) (http://tsd.dlink.com.tw/). You should only download firmware files with the "WW" (i.e. worldwide) designation in the filename.
-
Small update on my rollback to 1.05 after testing 1.06BETA.
My DNS-343 became unstable again. First slot1 was not detecting drive 1.
Then after changing the drive on drive1, box was no longer detecting drive 2.
Tested the drives on my computer.. No errors detected. No SMART errors also.
Did a Reset... reformated everything... working again.
Will recopy my data on it to see if issue happens again.
Ill keep you guys posted
-
Small update on my rollback to 1.05 after testing 1.06BETA.
My DNS-343 became unstable again. First slot1 was not detecting drive 1.
Then after changing the drive on drive1, box was no longer detecting drive 2.
Tested the drives on my computer.. No errors detected. No SMART errors also.
Did a Reset... reformated everything... working again.
Will recopy my data on it to see if issue happens again.
Ill keep you guys posted
Thank you for the update. I'm still perplexed as to why your NAS is behaving this way. No other reports of this type of issue have come across these boards.
-
I can confirm that I cannot change my device name in 1.06b1. Is it really safe to roll back to 1.05?
-
Thank you for the update. I'm still perplexed as to why your NAS is behaving this way. No other reports of this type of issue have come across these boards.
Just to let you know I have opened I support ticket with DLINK Canada.
And after 2 weeks of troubleshooting they decided to replace my unit.
Either a faulty motherboard or port.
Just received today my replacement. Will have it installed and test again.
Let you know later how it will go with 1.06B on it with the same drives.
-
Just to let you know I have opened I support ticket with DLINK Canada.
And after 2 weeks of troubleshooting they decided to replace my unit.
Either a faulty motherboard or port.
Just received today my replacement. Will have it installed and test again.
Let you know later how it will go with 1.06B on it with the same drives.
I recommend sticking with firmware v1.05. Version 1.06b01 has a minor fix to FTP, but has reported issues with soft-shutdowns hanging.
-
Is there anyone left in this forum. I was actually surpirsed to see entries from 2014 in here...but the last entry seems to be around March of 2104.
I still have one of these beasts laying around and would like to get it going again (DNS-343). Is the latest D-Link published firmware still v1.05 (or the beta 1.0601 with the FTP fix which seems to then cause other problems with some such as naming the unit and such)?
I see that last fellow who had problems with the Beta v1.06 was also operating in a RAID5 configuration and in one of his posts said he was using "new drives" during a post of his in 2013. I'm just curious that "new drives" he was using as the main issue with these units, and the smaller DNS-323 units seem to be the advent of teh 4k/Advance Format HDD drives that came out around 2006'ish?
Is anyone usine a "current" hard drive in these units and especially any current HDD in the 3TB or over capacity?
I'm not looking to RAID the unit...just looking for STABLE individual volumes or a JOBD format.
Hopefully somone is still around this forum...
I see there are some people working on a hacked firmware for the older DNS-323's, but not much out there for our DNS-343's....
Hope to hear from someone!
-
There was not much evolution from dlink or any other person on the firmware.
On my part I only have 1 dlink unit left. I sold all my units and switch to Qnap NAS that has more support and is more stable.
Its sad, since DLINK at one point was doing great... with support and evolution I had over 10 Dlink units... and when stability became crucial
I decide to move!
Good luck
-
Is there anyone left in this forum. I was actually surpirsed to see entries from 2014 in here...but the last entry seems to be around March of 2104.
I still have one of these beasts laying around and would like to get it going again (DNS-343). Is the latest D-Link published firmware still v1.05 (or the beta 1.0601 with the FTP fix which seems to then cause other problems with some such as naming the unit and such)?
I see that last fellow who had problems with the Beta v1.06 was also operating in a RAID5 configuration and in one of his posts said he was using "new drives" during a post of his in 2013. I'm just curious that "new drives" he was using as the main issue with these units, and the smaller DNS-323 units seem to be the advent of teh 4k/Advance Format HDD drives that came out around 2006'ish?
Is anyone usine a "current" hard drive in these units and especially any current HDD in the 3TB or over capacity?
I'm not looking to RAID the unit...just looking for STABLE individual volumes or a JOBD format.
Hopefully somone is still around this forum...
I see there are some people working on a hacked firmware for the older DNS-323's, but not much out there for our DNS-343's....
Hope to hear from someone!
DNS-343 - Can 2TB Advanced Format Drives Be Used In Firewar (http://forums.dlink.com/index.php?topic=61609.0)
-
The download link (ftp.dlink.com) appears to be down. Does anyone have an alternate link, or can anyone send me a copy they have themselves?
Thanks.
-
FTP was closed a while back. I'll check and see if they can post it to the new server.
From my understanding, the inherent risk associated with FTP in general due to the insecure login protocol (vs. secure FTP), trump any new risk introduced by passive vs. active mode. Passive does provide the benefit of allowing access that may otherwise be blocked by a firewall.
-
is there a place to get this firmware?
-
is there a place to get this firmware?
I recommend sticking with FW v1.05x as this version is more stable than v1.06.
I regressed to FW v1.05 on both of my DNS-343s.
-
Hi , i cant use passive ports on my DNS-343 , only beta 1.06b1 resolve this problem ? Any1 have link to 1.06b01 FW ?
-
When you say you can't use passive ports what do you mean?
Are you talking about passive FTP transfer, or are some ports blocked at your router/switch?
We have no problems using passive FTP transfer to/from our DNS-353 NAS boxes through the managed switch and they have the same firmware installed as when we bought them.
-
I need to set a specific range of ports to use FXP transfer from FTP outside my network (PUBLIC) to my NAS in my local network.
If this does not set a second server want to connect the random ports.
I must know what range of ports must be set on the router and that is why I need the functionality contained in 1.06b1:
It adds Passive port configuration to the FTP server.
"...Typically, the FTP server software has a configuration option to setup a range of the ports, the server will use. And the same range has to be opened/routed on the firewall/NAT....." and "...find out what ports is the FTP server configured to use. If you cannot know that, you have to open all unprivileged port range, 1024 - 65535. " I do not want to share all ports from the outside.
-
What are you proposing to use as the prime negotiating port on your NAS? You can set it to something other than the standard port 21 and the other ports fall into line as per RFC959.
Today I had my stores guy looking on the net for dns-343_b1_fw_v1.16b01 and it appears to have vanished into thin air (presumably when D-Link closed the FTP server all the beta software was dumped if more than 12 months old - makes one wonder about management at the time). Even the Russian site doesn't have it.
We use FXP between our mirror DNS-343 boxes and our clients DNS-343 for the full copy weekly backups and haven't seen any problems (FW1.04 and 1.05) but then we don't use routers at either end (we have a bank of managed switches that connect to the internet via a modem - our clients have the same except they have a single managed switch). I know this doesn't help you and unless someone (JavaLawyer) has a copy of the 1.06b01 firmware that they can send you I think you are stuck with what you have.