Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[billzinn]

So our DNS-323 has been in use for about nine months with no problems till now...
Today, tho, one of our 'users' created a folder and a single file that simply contains an 'index' of other files related to a project.  Having created the file with its initial contents and then 'saving' it to the location we need, she is now unable to 'open' the file to alter the contents again.
ALL of our users get an error message saying "...Access denied. Contact your administrator..".
She (as well as three others) have 'full access' (R/W) permissions to the entire volume AS WELL AS this folder. But currently, no matter what we try, everyone gets this same error message now.
If it wasn't for the fact that the amount of 'work' that went into the creation of the initial file represents two full days of effort, I'd simply delete it (uh, if possible) - but if we can reaquire access I'd prefer NOT having to do this .... (BTW: it is a Word 2007 document).
So - any hope of retrieving this file or shall I just put her to work re-creating the file?
But of much higher curiosity: Does anyone have any clues as to what the *&@% happened? - or shall I continue to simply blame Microsoft...?
Hmh... no doubt it is probably something to do with "The Redmond Crowd" ...
Windows XP Pro and Office 2007 SBE are FAVORITES of mine, especially....

[gunrunnerjohn]

One of the old standbys is to reset the box to factory defaults and reconfigure.

[dosborne]

Ensure your firmware is up to date. There was an issue in older versions saving some M$ office files.

[gunrunnerjohn]

And make sure you reset to defaults whenever you update the firmware!

[Caretaker]

You might want to check the rw permissions of this specific file itself.

[billzinn]

Well... I reset it to 'factory defaults' - updated the firmware to ver. 1.09 (latest) - and still cannot set any attributes, rights or permissions on this or several other files that I've found (since) within a couple of other folders.  What I've been trying to do is (using my PC and logging into the NAS as the administrator) set the attributes to R/W for all users and groups, but I still cannot 'reset' anything on these files.
From the NAS control page, the folder(s) in question are 'marked' as R/W for everyone but this seems to have no effect.  So - we've 'lost control' over these files, it seems.... and God knows how many others might also be similarly 'affected'....
Bummer....

[dosborne]

You may have to consider going the unsupported route and install FFP in order to recover the permissions. At a minimum, you could create a simple fun_plug script that resets the permissions of the folders/files that you have already identified.


http://forums.dlink.com/index.php?topic=2183.0

[jamieburchell]

There's a "reset network access list" button in the web admin, did you try that?
I can't think how any files could have their file permissions set incorrectly when using simple SMB access - assuming that's what you are doing.

You don't need to install FFP to get this fixed. You can create a single fun_plug file in the root of Volume_1 with commands that will sort out file permissions.

[billzinn]

It would appear that there might possibly be 'a problem' with this NAS, on more of a  'firmware' or 'hardware' level, or so I suspect.
When resetting the  network access to factory defaults, all files on the hard disks are fully available (Volume_1 is given 'R/W' access to all users) and the 15 files that were not accessible can now be assigned the necessary access rights (R/W).
But this can only be accomplished when there are no user accounts or if there is a single user account.  When more than a single user account is added, all 15 files that were seemingly 'locked' are once again 'locked' and cannot be accessed or copied to another location, so I must presume this is a 'failure' on some part of the emedded Linux OS.
Having re-established some level of 'control' over the entire NAS file structure finally, we've decided to 'move' the entire contents of the file system to a 'spare' Windows XP box and simply access these via a 'peer-to-peer' Windows network - for now.
When I have the opportunity, I will install new hard disks (I 'suspect' one of the two drives that are now in RAID-1 configuration - and they are decidely too small, now, also ... 160 GB isn't what it once was, by today's considerations), and then 're-flash' the firmware with these new totally empty hard disks  - and then see if this is still 'an issue'...

[gunrunnerjohn]

FWIW, I've never run into this with either the DNS-321 and DNS-323, both have multiple user accounts.  The only user account issue that currently exists is known, that being that you can't mix anonymous and password protected shares on the box.

[billzinn]

Since there has never been any 'anonymous' user access allowed on the NAS, it sorta 'confuses' me that adding anything more than a single user account would cause this to happen - which is why I have a suspicion about either the hardware, or the 'vailidity' of that most recent firmware update (1.09).
I have two 'brand-new' 1 TB Seagate disks (originally intended for use in the 'senior partners' PCs) that I am just now 'unwrapping' and will install into the NAS.  Fingers crossed, once the NAS has 'mirrored' them, I will create three user accounts and attempt to upload a couple of GB of data (IE: the folders that contained these 'locked' files) and then verify things work 'as advertised'.
At the very least, the project is 'saved' and we can continue to function - but I do very much like this NAS and I want to see if I can 'return to service' with 1TB of disk space now. Hopefully, if things 'go' OK, it be an even better resource than it was before...  I'll post my findings once this is acomplished.

[gunrunnerjohn]

It shouldn't have that issue, at least that's the first I've heard of it.  My major complaint with the box is just the performance, but it has remembered just fine.

[billzinn]

Heh-heh... One thing this HAS accomplished for me, tho, is a 'renewed interest' (on the part of the owners) in much better backup capacities.  I've gotten approval (and a budget) from 'the boss' to configure MULTIPLE backup points across the network AND (at last) approval for 'off-site' backup. Geez... I've only been '*****in' about that for - oh, maybe A YEAR..!!

[jamieburchell]

I'm sure the problem will go away if you install fresh disks in the NAS and format them, then copy the files back.