D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: thecreator on February 25, 2009, 07:32:17 AM
-
Hi Support,
I would like the ability to have the same Workgroup Name throughout my Network, on Computers and the DNS-323 Storage Device and I can't.
I have Comcast Internet and when I first got Comcast the Technician set up the Computer Workgroup to read @Comcast and I have been using the "@" symbol as part of the Workgroup in all my Computers and in the new Windows 7 Ultimate 32-bit and 64-bit Beta Versions without a problem.
Then I purchased the DNS-323 Storage Device and when I typed in the Workgroup Name that I am using, the unit gave me an error message for an illegal character.
How can I get the DSN-323 to accept @Comcast without problems?
-
That's a really strange workgroup name- it really doesn't jive with modern naming conventions espeically in respect of how Windows handles DNS and name resolution. It makes your computers look like email addresses in DNS: computer@comcast - and if you have windows registering your computer in DNS with your 655, it creates a name like computer.@comcast.comcast.net when it should be computer.workgroup.comcast.net.
Sometimes, just because you can do something doesn't mean you should do it.
-
Hows about a mini file-manager type app built in to either the admin utility or the download utility so you can move files or folders between volumes without using a middle man pc?
Robert
Otter River, Massachusetts
-
i second that (file manager)it would greatly save on network bandwith and time
-
Two wishes
1. Log file or some way to get feedback to report/identify errors when the UPNP server is indexing the files. For example some files in my music folder are causing the DNS-323 not to serve up the entire music collection (i am guessing) . I am slowly adding 1 artist folder at a time, and checking the music blade on my xbox 360. to see if all files have been transfered, it takes a while.
2. This little box does standard formatting, Raid 0, Raid 1 and some other one JBOD(?). Many people are buying this device as a media server / backup solution. Right now I am certain alot of people are running in RAID 1 and thinking that all their stuff is backed up well. What I would like to see is some sort of front end for rsync and cron (or whatever) in the default webpage to schedule backups from Volume_1 to Volume_2. It would be best if after the initial backup that subsequent backups only copied changes. This would have us using Volume_1 as a storage drive and Volume_2 just for a backup of Volume_1.
Thanks for the continued support.
-
FTP over SSL/TLS options and documentation
----
WOL (wake on lan)
----
file manager
----
schedule device on/off
----
auto power recovery
---
recycle bin
---
tools -> device info -> HDD S.M.A.R.T. messages
tools -> device info -> HDD S.M.A.R.T gui to run tests
---
hdparm/sdparm support (disk management/tuning tool)
---
comprehensive diagnostic tool
---
alerts (not email alerts) due to disk failure
alerts (not email alerts) if Raid rebuilt
alerts (not email alerts) if system temperature exceeds xxx
---
ext4 filesystem support. Firmware 1.02b removed ext3 filesystem support. The ext4 filesystem is backward compatible with ext3 and ext2, making it possible to mount ext3 and ext2 filesystems as ext4.
---
NTFS 3.1 support which covers the following:
Windows XP (autumn 2001; "NTFS V5.1")
Windows Server 2003 (spring 2003; occasionally "NTFS V5.2")
Windows Vista (mid-2005) (occasionally "NTFS V6.0") and Windows Server 2008)
*if enabled, users would be able to run a variety of programs : anti-virus, defrag, encryption etc.*
---
Active Directory support/domain authentication
---
customized Volume name(s)
---
gui filesystem integrity support (defrag/chkdsk/fsck)
---
customized Administrator login name other than 'admin'
---
status -> device info -> Uptime
status -> device info -> Last Rebooted
status -> device info -> Last Shutdown
status -> device info -> Last Email Alert Sent
status -> device info -> Current Fan Speed
---
tools -> power management -> Shutdown System After Temperature Exceeds xxx
---
Graphically showing system temperature over xxx period of time
Graphically showing NAS network input/output over xxx period of time
---
tools -> Fan Management -> Fan Settings: Low RPMS=xxx; Medium RPMS= xxx; High RPMS=xxx
tools -> Fan Management Options-> Default Fan Speed (Low/Medium/High)
tools -> Fan Management Options -> Turn Fan To Low When Hibernating or Temperature Reaches xxx
tools -> Fan Management Options -> Turn Fan To Medium When System Temperature Reaches xxx
tools -> Fan Management Options -> Turn Fan To High When System Temperature Reaches xxx
tools -> Fan Management Options -> Shutdown System After Temperature Exceeds xxx
-
+1
---
NTFS 3.1 Support
---
filesystem integrity support (defrag/chkdsk/fsck)
---
customized Administrator login name other than 'admin'
-
Please add the ability to assign users to multiple groups.
-
I would like the ability to set the fan temperature trigger lower than your default and the also be able to set the fan speed for the low setting. I can hear the fan at 2500 rpm, but I hear absolutely nothing at 2000 rpm.
My default would be to have low speed fan turn on at 2000 rpm at 42C.
-
Add port number for SMTP server on the email alerts. My ISP uses a non-standard port.
Thanks.
-
One request
FXP FTP support
-
Better BT and Emule client.
Andy
-
FTP over SSL/TLS options and documentation
----
WOL (wake on lan)
----
file manager
----
schedule device on/off
----
auto power recovery
---
recycle bin
---
tools -> device info -> HDD S.M.A.R.T. messages
tools -> device info -> HDD S.M.A.R.T gui to run tests
---
hdparm/sdparm support (disk management/tuning tool)
---
comprehensive diagnostic tool
---
alerts (not email alerts) due to disk failure
alerts (not email alerts) if Raid rebuilt
alerts (not email alerts) if system temperature exceeds xxx
---
ext4 filesystem support. Firmware 1.02b removed ext3 filesystem support. The ext4 filesystem is backward compatible with ext3 and ext2, making it possible to mount ext3 and ext2 filesystems as ext4.
---
NTFS 3.1 support which covers the following:
Windows XP (autumn 2001; "NTFS V5.1")
Windows Server 2003 (spring 2003; occasionally "NTFS V5.2")
Windows Vista (mid-2005) (occasionally "NTFS V6.0") and Windows Server 2008)
*if enabled, users would be able to run a variety of programs : anti-virus, defrag, encryption etc.*
---
Active Directory support/domain authentication
---
customized Volume name(s)
---
gui filesystem integrity support (defrag/chkdsk/fsck)
---
customized Administrator login name other than 'admin'
---
status -> device info -> Uptime
status -> device info -> Last Rebooted
status -> device info -> Last Shutdown
status -> device info -> Last Email Alert Sent
status -> device info -> Current Fan Speed
---
tools -> power management -> Shutdown System After Temperature Exceeds xxx
---
Graphically showing system temperature over xxx period of time
Graphically showing NAS network input/output over xxx period of time
---
tools -> Fan Management -> Fan Settings: Low RPMS=xxx; Medium RPMS= xxx; High RPMS=xxx
tools -> Fan Management Options-> Default Fan Speed (Low/Medium/High)
tools -> Fan Management Options -> Turn Fan To Low When Hibernating or Temperature Reaches xxx
tools -> Fan Management Options -> Turn Fan To Medium When System Temperature Reaches xxx
tools -> Fan Management Options -> Turn Fan To High When System Temperature Reaches xxx
tools -> Fan Management Options -> Shutdown System After Temperature Exceeds xxx
Amen Brother. I second all of this for 1.07
-
support for Deskstar 7K1000.B - Model HDT721010SLA360
PLEASE!!
-
Tools for drive managment defrag, struture repair and troubleshoot configuration
Reset and reformat drive should not be THE solution to fix all problems.
-
other bt client other than the default one
1. option to enable encrypted legacy connections
2. option to shut down dns-323 upon completion of all downloads(such option is available with uTorrent program)
3. NTFS support
4. usb port(support for other usb drives)
-
1. Remove please that Web Utility ERROR
Access Error: Site or Page Not Found
when trying to obtain /web/login.asp?id=7961455
Cannot open URL
which is comming after auto admin's logout realised by machine after idle time, customized in advanced section. PLEASE. Switch on/ off of the DNS is not propper resolving that error.
2. We live in SMART ages and other advanced disk technologies, why we have no one tool for manage of the disk as defrag, identification of the condition etc.?
THANKS.
-
support SONY 40W4500. When I use DNS-323 as media server for SONY 40W4500 only 1024 x 768 and lower photos DNS-323 media server shows.
-
How about the ability to view more than only 2000 files at once. Oh, and anti-hack features like ip blocking after 3 incorrect login attempts...
-
Add the following to the wishlist v1.07:
- HTTP server (many similar products offer this)
- Improve FTP log
- Improve the USB port usage (UPS, Additional HD, etc)
-
Fix old bugs:
- "Adding an extra disc can wipe data on existing drive!" bug
- Everybody can access BT Page without authentication using direct link: http://<put_your_dns_ip_here>/web/bt/fe02.asp
- http://forums.dlink.com/index.php?topic=1776.0
-
This is copy of wishlist topic from manolito2112 and others, think is better have one wishlist.
- Bittorrent Downloads complete notification
- same share with multiples user permissions
- folders manipulation via GUI
- snmp
- remove unnecesary DHCP server ( any router provide more advanced DHCP server )
- Confirmation that a USB UPS and printer co-exists
- Ability to view status of USB UPS and printer
- UPS monitoring and control
- Improved UPS configuration; let me configure DNS with information pertaining to the UPS that's connected or determine such automatically. In other words: remove loading of multiple drivers (upsdrvctrl and ups.conf) as means of establish which UPS is connected! This will also improve boot-up time.
- RSYNC will take the device to a professional level, please include RSYNC
- allow use some characters in usernames (for example dot ".") to able use john.m username
-
- Bittorrent Downloads completed notification
- same share with multiples user permissions
- bettler file manager , ability to move folder
- snmp ( storage,host,network MIBs )
- remove unnecesary DHCP server
- RSYNC protocol ( client and Server )
- Power up and shutdown by schedule
- UPnP controller to perform actions like adding and removing port mappings for
FTP server ( passive mode )
to be continued.....
-
Please make change in HDD hibernation time.
Not from drop-down menu but writable in minutes / hours will be better.
30 min is too short.
Thanks
Janekx
-
Definitely a more reliable Torrent client.
Andy
-
-NFS (Network file system)
-
I'd like to be able to add multiple users with different access permissions to the same folder. For example:
Say I have a folder named "Media, I'd like to have say one user with R/W permissions and all other users with "Read Only" access.
The way it works now, a new share is created with a "-1" added to it. This is too messy. Please fix.
-
1. Add the function to BT individual file in seed.
2. support FTPS protocol
3. remote access to "config" and "download" GUI from Internet.
Thanks!!
-
3. remote access to "config" and "download" GUI from Internet.
Thanks!!
X2
-
- EXT3 is a must! (with EXT2 -> EXT3 conversion tool)
- UPnP AV: support for MKV, OGG, FLAC
- web interface redesign: use AJAX technology (especially for replacing old scripts like schedule downloads status with stupid manual refresh button)
- Schedule downloads: remove URL length limit, unit has a problem with masked links using PHP scripts
- plugin support (like QNAP's QPKG packages)
- defragmentation tool
-
I'd like to be able to add multiple users with different access permissions to the same folder. For example:
Say I have a folder named "Media, I'd like to have say one user with R/W permissions and all other users with "Read Only" access.
The way it works now, a new share is created with a "-1" added to it. This is too messy. Please fix.
All those shares can point to the same folder. Try it.
-
All those shares can point to the same folder. Try it.
just because something works does not mean it is the best option. I can see the easiest implementation was chosen.
I don't want dir-1 dir-2 dir-3 shares when telling people to connect to the dir shar.
that and all are visible you get more then two then you are clicking trying to remember which is correct.
it is 1 thing in an enviroment where you have 1 user on a single computer. quite another when you have more.
-
1. FLAC support for UPnP AV server.
2. Allow special characters in user authentication passwords.
-
I'd be happy with just fixing the bugs from 1.06. My main problem is the disks coming out of hibernation constantly, when there are no computers turned on and connected.
-
The way the DNS-323 handles permissions is a bit weird. I'm starting to understand a bit more but it's still not a very good system. I hope that these flaws can be addressed, because as it stands the device isn't much more than a toy.
By default, the root of the storage volumes on the device give RW permissions to All. Obviously, this isn't secure, but leaving it wide-open makes it easy to access out of the box without forcing the user to do configuration, so I don't mind this choice.
Securing the device is a bit weird. The permissions are share-based. What this means is, if you want to set up permissions for some directory on the storage volume, you are basically creating a share to that directory each time you set another permission rule. This is fairly non-intuitive and un-windows-like.
Finally, no share can be accessed unless All is granted at least Read-Only permissions.
I'll explain how this works a bit better by using an example.
Let's say I want to have a directory on Volume_1 that I want to share out in a secured manner. Here's what I do:
- Make the dir.
- Set permissions rules for the dir:
- Read-only to All
- Read-Write to the user or group that I want to be able to write to the share.
- If I have more than one user or group, one rule for each user or group that I want to add to the share.
What happens is this:
- dir is created on the filesystem of Volume_1
- The following shares are created
- A share to \\dns-323\dir is created with read-only perms assigned to All.
- A second share is created to \\dns-323\dir-1 with RW perms assigned to User.
- Subsequent shares are created to \\dns-323\dir-N with RW perms assigned to the user or group.
Now, if I want to connect to the share, it gets a little complicated. If I browse to \\dns-323\dir I get in, but I have read-only perms because this share grants read-only to All.
Say I want to be able to write to the file, though. To do that, I have to browse to \\dns-323\dir-1 and pass authentication as the user who I granted permissions to. The dir and dir-1 shares aren't really directories, but rather are shares which points to dir.
This is where it gets weird. On Windows, if I want to connect to the dir-1 share, the authentication seems to require BOTH Guest AND [User] to be passed to the server in order for access to be granted.
Say I browse to \\dns-323\dir-1 so I can write files. The server challenges me for authentication credentials twice. First, I'm prompted to authenticate as Guest. Guest's password is blank, and should be authenticated automatically, unless there is no All rule for the share. If All doesn't at least have read-only, you can't get past this point. So there's really no way to deny access to All at the share level. Next, I'm prompted to authenticate as the User who I granted permissions to the dir-1 share. So I type in the password for User, and if I entered it correctly, I'm granted access to the share, and I can read and write files. Yay.
OK, so far so good. But lets say I want to create a share which is not open to All. I want it secure so that guests on the network can't get in. I can't do this. If Guest doesn't at least have read-only access, I can't proceed to connect to the share. The only way to secure files on the device is to not share it at all, which of course is completely pointless. There's no explicit deny, and to gain access to any share, I have to have read-only for Guest AND read-only or read-write for the User or Group.
This means that the device isn't very secure at all. The only thing protecting it from the outside world is the perimeter firewall on my router. Anyone on the LAN can read and copy files from the system, unless I choose to put them onto a directory that doesn't have any shares associated with it.
It's a little bit better if you're connecting via FTP rather than CIFS/SMB. The DNS-323 allows the administrator to set up FTP Access Lists, and while you can't disable anonymous login for FTP, you can set up an empty default directory for Anonymous login and grant read-only permissions there. Thus, if someone connects to your FTP server anonymously, they're trapped in an empty directory, can't navigate out of it, and can't write files. At that point the only damage they can do is they're taking up one of the available connections to the FTP service, of which you can only allow a maximum of 10. If you get 10 guests logged in, they can cause a Denial of Service condition, making FTP unavailable to any legitimate users until one of those 10 connection slots opens up. The FTP server will time out idle connections after a few minutes, but there's nothing to prevent your attacker from continuously trying to connect to the device, picking up any open connection slots that free up a few milliseconds after they become available.
Additionally, with FTP, while the DNS-323 does support SFTP, it's not at all obvious how to connect securely. Secure FTP is enabled if FTP is enabled, but there's nothing to tell you how to connect via SFTP -- I had to read the user discussion forums to learn how. Worse, there's no way to turn off regular FTP access. So if you choose to have FTP enabled at all, you are open to being attacked by the anonymous DoS exploit. And as long as you connect via regular FTP, your authentication is passing in clear text and thus can be sniffed by malicious eavesdropper on the network, who can then steal your credentials and access the FTP shares. On top of that, there's no logging available, so you have no idea what's going on.
The conclusions I take from this are that the DNS-323 is really a toy device, not something for serious use. I'm not even saying it's a home network device as opposed to a professional or enterprise class device. You really can't use it to store anything that you don't mind sharing out to anyone and everyone who has access to your network. Security is as important to home users as it is to corporate enterprises. It's not like it costs more to implement correct paradigms in access and permissions. These are basic problems that have solutions that are decades old. I'm not sure why they're so badly mangled on this product. Is it really this broken? Or am I missing something?
For the purpose I bought it for, it's not even really well suited. I'm not so concerned about protecting my ripped CD collection against unauthorized access, although I'd really prefer it if I could prevent unauthorized access, but it won't serve FLAC files over its UPnP service, and I'll need to install a 3rd party software hack in order to enable this.
All these problems are solvable, as it's just a matter of improving the firmware to the point where it can secure shares adequately. Hopefully D-Link will address these things in a future revision.
-
What I'd like is the ability to add an additional hard disk via USB. Right now the only way to do this is through a custom script and workaround but I do not feel safe doing it. It would be nice if I can just "Plug It In" and go. I don't care if I have to format the external USB drive into ext2 or ext3.
Also, a disk defragmenter utility would be nice.
-
1. Set the speed for ftp server but by time.
Exemple : 8:00 am to 17:00 pm speed limit is 100kbits/sec.
17:00 to 8:00 no limit speed.
etc
-
I would like to see, in order of importance. (please):
HTTP deamon wiff CGI scripts (or even plain HTTPD)
USB hard drives WITH NTFS SUPPORT
Advanced logging
Ability to ONLY allow secure FTP
A binary USENET leecher + Extractor + NZB (pipe dream I know)
Thanks!