All builtin user names cannot be added into Security or Sharing ?

We have AD 2003. We tried to assigned the permission using the Builtin objects, for example, Users, Administrators, Guests, or Backup Operators, etc. We just found out we are not able to. It simply just said "The object name cannot be found."
What could be wrong? Please help.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ok i haven't done something like that in ages, but i do want to help if i can. So i have one suggestion, dont blame me if i'm wrong :)

Try using domain name in front of the usergroup
CastlewoodAuthor Commented:
No, still not working with the domain name in front.
I also verified the 'Built-in security principals' is ticked for the Object type.
I'm wondering if there somewhere is a policy restricting it??
Its not a policy restricting it. Because in that case it wouldn't search at all, nor give you the error it couldn't find anything.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

CastlewoodAuthor Commented:
Okay, I found more details....
I found the Builtin user group names are available for setting up permission on the AD servers only. All other member servers don't recognize the Builtin names even the Builtin are defined in ADUC and supposed for the whole AD Domain, correct? Please help.
Can you verify if it is the case in your environment?
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
I think this is by design. I'm getting the same results.
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
It is by design.

If you check the group scope on the DC, it shows "Built-In Local" and can only be used to assign permissions to resources on domain controllers.

Edit -  Here's some better links:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.