Print

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

[Roger1234]

When I try to create a new user account under User Settings, called administrator I get an error message.  The error message is "This account does not accepted . Please try again."  Current firmware is 1.01

Has anyone else run into this?

[JavaLawyer]

When I try to create a new user account under User Settings, called administrator I get an error message.  The error message is "This account does not accepted . Please try again."  Current firmware is 1.01

Has anyone else run into this?

Yes. The names Administrator and administrator are reserved by the ShareCenter. The same constraint exists on the DNS-345.

[Roger1234]

Thanks for the quick reply!
I can't imagine why in the world D-Link would code in a restriction like that, it is unlike my other NAS a D-Link DNS-321.  Are there any known ways to get around this, without hacking the thing?  There is no way I want to go around and rename the administrator account on all my systems.

[JavaLawyer]

I'm not aware of any workaround to use "Administrator". I have a DNS-343 which is part of the legacy firmware family (as is the DNS-321) and that constraint doesn't exist. All of the ShareCenters (dating back to the DNS-321) have the default Admin account. Why won't that suffice?

[Roger1234]

Sorry, I should have been more specific.  The admin account is fine for administrating the nas, but I need an account called administrator to read/write the nas.  I have about 10 windows systems in active directory and most of them do unattended backups on a schedule, running under the administrator account.  On the DNS-321 I simply created a account with administrator/<password> for backups.

[JavaLawyer]

Perhaps the name was reserved to avoid possible confusion with the admin user account, i.e. there can only be one master admin, and the names can be confusing if the account isn't routinely accessed.

[bazong]

i was looking for a solution for this problem!
Why must some developers on their dark desk try to think for the administrators?
A lot of D Link Nas are sold from me as backup stations.
Cause D-Link dissalows me to give a user the name Administrator, i have
to Change dozends of configurations and test them again.
Maybe the next NAS is from an other brand.

So much IT trouble is only why people add non neccessery features!

I say: who is dissabling an account named "Administrator" has no idea
what happens in the field.

If you are administrator, should you login with a new account for any task?
What if the next it-zombie disables the user admin?

oh my dear...

bye
  juergen

[JavaLawyer]

Whatever the reason, the username administrator appears to be reserved on all of the newer ShareCenter models. I'll add this to the wishlist for each product. 

[bazong]

if somebody from d-link will read this:
this may help!
thanks

[JavaLawyer]

No problem. I'll also see what else (if anything) I can find out.

[JavaLawyer]

I have an answer from D-Link. For the newer ShareCenter models the username administrator is reserved for root access (Linux) to the ShareCenter. At present, the name can't be re-used for that reason.

[bazong]

Buggy development...
what i say, since 25 years it:
too many it developers see only their own desk...

[JavaLawyer]

Buggy development...
what i say, since 25 years it:
too many it developers see only their own desk...

Since this implementation was intended, I wouldn't necessarily call this a bug. In any event, I placed the request directly with D-Link to see if they can perhaps address this in future FW iterations.

[bazong]

Shure: itīs not a true bug.
But if developers donīt think about the use of their products,
the effect is the same like a bug.
So far i will buy nas from other brands.
Why should i add another user, why should i rework all the scripts
at different customers?
Why do a workaround if the workaround is not necessary?
Thank you for the moment.
Ciao
   Jürgen