D-Link Forums
The Graveyard - Products No Longer Supported => DNS-323 => D-Link Storage => Beta code! => Topic started by: energyweapon on December 03, 2009, 12:13:47 PM
-
I have two 323. Just flashed one of them (with two Samsung 1.5 TB in RAID1) to 1.08b8. I will wait a while to flash the second one.
-
No issues with me either so far except that i can't get the email SMTP authentication to work even though i'm entering the proper username, email address. smtp address, port 25 (i will need to double check this port with my ISP, i'm almost sure this is what they use).
-
No issues with me either so far except that i can't get the email SMTP authentication to work even though i'm entering the proper username, email address. smtp address, port 25 (i will need to double check this port with my ISP, i'm almost sure this is what they use).
Most ISP's don't use 25 anymore because of spammers. I would double check this with your ISP.
-
My ISP uses 25 - if I check SMTP authentication the mail sending will fail, uncheck it, it goes through.
-
Most ISP's don't use 25 anymore because of spammers. I would double check this with your ISP.
I confirmed my ISP is using port 25 for SMTP (smtp.telus.net) for the mail server account i have with them. I was doing an experiment and basically as long that I have Login method=account, Authentication=unchecked, port=25, SMTP server=smtp.telus.net, the rest of the fields can be anything, for example username=test, password=1234, Sender email=test@bugsbunny.com and receiver email=my email address. Doing this i would still get an email, almost seems like it's the same as having it as Anonymous mode. Below is the email i got:
=================
> Date: Thu, 3 Dec 2009 20:55:02 -0700
> From: test@bugsbunny.com
> To: ngarcia1981@hotmail.com
> Subject: dlink-E24A91_E-Mail_Alert
>
> This is a test e-mail.
>
> Sincerely,
> Your DNS-323
=================
Anyways, this really isn't an issue for me, as long that i can get email alerts one way or another i'm happy.
One other thing i noticed, last night after installing the new beta build (properly followed all the instructions), because the previous firmware i had was 1.07, I installed the Bittorrent package for the first time, i decided to reset the router after doing this as well. Well my point is this morning the temperature of my dns323 was at 42C, i thought it was pretty hot due to the fact that the DNS323 is located in my basement near a window where the outside weather currently is -15C, inside probably 10-15C. So before i left for work i completely disabled the Bittorrent application, this evening when i checked the temperature again it was pretty normal at 28C. I will enable the Bittorrent application again and check the temp in the morning. Also want to add i have no files downloading/uploading with bittorrent.
-
This morning the temperature on my D-link was 39C. This is with Bittorent add-on enabled and nothing uploading/dowloading. I will keep the Bittorrent addon enabled for one more day and then disable it to see if the temperature changes.
-
I flashed my DNS-323 with the new beta, still working fine, and I didn't have to restore any data. ;D Haven't really noticed any difference...
-
Last night the temp was at 39C then i disabled the addon bittorrent and this morning when i checked the temp was at 34C. Can it be that this package makes your DNS323 run about 5 degrees warmer, even though i was not downloading/uploading files?
-
Other folks have mentioned that some of the add-ons like uPnP seem to cause processes to run at 100% CPU, this could account for the temperature rise.
-
Could be, i never noticed the high temperatures using 1.07 though.
-
Here it has 40°C when waking up from Power Safe.
But it is almost the same as it was with 1.08b05 and b07.
When running under full load it will not exceed 43-45°C.
So no problem for me. I think nothing has changed.
Btw. the metal case keeps cool when in powersafe mode.
-
Power LED control still doesn't work - that's all I want to work - arrgh!
-
I'm curious, what do you want the power LED to do?
-
Power LED control still doesn't work - that's all I want to work - arrgh!
Power LED control does work - did you reboot?
-
Loaded new firmware, reset to factory defaults, rebooted (multiple times). I've got 3 DNS-323s - doesn't work on any.
-
I'm curious, what do you want the power LED to do?
I want it to be off! They added the ability in 1.08 but it's never worked for me.
-
Doesn't work here either :(
-
Loaded new firmware, reset to factory defaults, rebooted (multiple times). I've got 3 DNS-323s - doesn't work on any.
Are you disabling it in Tools/System? It's off on mine - either that or the LED coincidentally stopped working at the same time.
Edit - a reboot is not required - I misread the popup message that tells you the LED flashes during a reboot before going out - I can enable/disable the power LED at will from the Tools/System menu.
-
The release note says it's now possible to set the FTP port other than default port 21. However, if I set mine to (for example) port 8919, it doesnt work.
Setup:
Linksys WRT320N on DD-WRT v24-sp2 (11/25/09) big
FTP port 21 forwarded to 8919 at static IP address of the NAS set by the Linksys WRT320N.
DNS-323 (HW Ver B1)
FTP port set to 8919
If I try to connect to www.myftp.com, I get to the point of accepting the username/password... but then it time outs. If I, however, change the FTP port in the DNS-323 to port 21 (default) and I reverse the port forwarding to port 8919 forwarded to 21 at static IP address set by the Linksys router, when I try to access www.myftp.com:8919, I could get through and see the content of my FTP.
-
Not sure it's the DNS-323 that's the issue. I just changed my FTP port to 8021, and it worked flawlessly, just as I'd expect. I didn't try an external request, but I have no reason to believe it would behave in a different manner.
-
Have you tried setting the passive mode transfers setting for the ftp client on/off?
-
Are you disabling it in Tools/System? It's off on mine - either that or the LED coincidentally stopped working at the same time.
Edit - a reboot is not required - I misread the popup message that tells you the LED flashes during a reboot before going out - I can enable/disable the power LED at will from the Tools/System menu.
Yep - I am disabling it. I have to admit I find the wording of the setting a bit confusing -
Power LED Control enable/disable.
First possibility is 'I want to control the power LED so hit enable'
Second is 'I want to disable the power LED so hit disable'
The pop-up when you hit 'disable' gives the game away as to what the correct setting should be though (I've tried both settings just to be sure) but no - lights stay on for me.
Does it disable all the LEDs for you (2 drive, 1 power, 1 activity) or just the power LED?
-
When you disable it, you have to restart the DNS-323 to actually see the effect.
Rebooting after disabling it to test...
Once the reboot finished, the power light is off. The two disk status lights and the network activity light are still working.
Note that the power light stayed on after setting the option until I rebooted the DNS-323.
-
Does it disable all the LEDs for you (2 drive, 1 power, 1 activity) or just the power LED?
Just the power LED - isn't that what it says?
-
Just the power LED - ah OK. It seems somewhat pointless just turning off one LED when the other 3 are lit (and bright even when there's no activity) though?
The release notes for the beta say:
27. Add the Ability to control the devices LED status of On or Off. Some users are complaining about the brightness of the BLUE LED when the device is placed in their home.
I would've expected this to mean all LEDs but yep. I guess they just mean the power LED.
Can I add a request to be able to switch off all the LEDS in a future beta then? Most of my other devices allow this.
-
The release note says it's now possible to set the FTP port other than default port 21. However, if I set mine to (for example) port 8919, it doesnt work.
Setup:
Linksys WRT320N on DD-WRT v24-sp2 (11/25/09) big
FTP port 21 forwarded to 8919 at static IP address of the NAS set by the Linksys WRT320N.
DNS-323 (HW Ver B1)
FTP port set to 8919
If I try to connect to www.myftp.com, I get to the point of accepting the username/password... but then it time outs. If I, however, change the FTP port in the DNS-323 to port 21 (default) and I reverse the port forwarding to port 8919 forwarded to 21 at static IP address set by the Linksys router, when I try to access www.myftp.com:8919, I could get through and see the content of my FTP.
This sounds like the client side firewall is blocking the data channel - most late model NAT firewall/routers know to expect an incoming data connection after the initial outgoing connection on port 21, but, if a non standard port is used, they don't recognize the connections as ftp and block the incoming request.
Did you configure passive ftp? If not you have two choices - get the client from behind the NAT router - or - configure the server side NAT router AND the DNS-323 for passive ftp.
-
Can I add a request to be able to switch off all the LEDS in a future beta then? Most of my other devices allow this.
Here's the kit to turn off the other LEDs. :D
(http://www.jamestowndistributors.com/userportal/woeimages/Tape/8913.jpg)
-
lulz
-
Here's the kit to turn off the other LEDs. :D
(http://www.jamestowndistributors.com/userportal/woeimages/Tape/8913.jpg)
funnily enough that's exactly what I use! My problem is the dns-323s are in a spare bedroom, which isn't used that much but isn't a big room (10'x10') and you really notice the dns-323s when they're a few feet from your head! I've taped up the fronts but there's still a lot of light leakage round the back through the fan holes etc. Also a few other devices like a 16 port netgear switch don't help either... It's certainly festive anyway.
-
I'm glad I don't sleep in my office! There's a router, a VoIP box, three Ethernet switches, the DNS-323, and several printers that are in standby, but have lights. Talk about being lit up! :D