Windows 2003 Standard Server

I upgraded a Windoes 2000 Standard Server to Windows 2003 Standard.  Now when I try to add a computer an error messsage comes up "access denied" and I'm unable to add the machine.  I've tried renaming the machine to a different name, also tried outting the server in to a different workgroup, but nothing.  Please help!!!
Lou PereiraAsked:
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.

Check the DNS settings on the computer you are trying to add.  They should be pointing to the new 2003 server.  Also, try using the fully qualified domain name of the domain when joining.

Additionally, any strange errors in the event logs of either server?

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
Does the account you are using have Admin rights to add computers to the domain?  Check your Group Policies under:

Computer Configuration\Local Policies\User Rights Assignment
Policy:  Add Workstations to Domain

Are you running server as a DC? If so, are you using DHCP?
There are things that can go "Wrong" after such an operation, but I doubt the install went bad.
Most likely culprit is the network settings. I noticed the last time I setup a 2k3 server that it applied the static IP I specified, but the networking was still assigned DHCP. Like I said, an IPconfig showed my static entry, but a quick check of the network settings (Had a misconfigured secondary DNS entry, pointed at my ISP...) had the silly obtain automatically enabled. Most services like DHCP and DNS don't like to work on a dynamic address, and will often fail to load. Among these would be AD; and without AD, and more importantly, the RID Master FSMO holder present, it won't allow a machine add. Speaking of which, have you checked your FSMO roleholders?
Obviously, that would be where the ultimate failure is occuring. But it is possible the client OS is trying to unregister from the old machine.
Hmmm... have I overcomlicated things?
Take it one step at a time, start with the networking, make sure the entries are correct for TCP/IP.
then see if the server can identify the FSMO role holders.
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.