Can't create new user accounts on 2003 server

Hi, I had a windows 2000 server that was failing, I got a new 2003 server, connected it to the domain and was able to manage users on it, after I transfered the shares on to the new server, added dns and verified all I figured the new server was managing everything, especially since the clients were using its ip address as the primary dns server.

Then the old 200 server died, now most everything seems fine on the client side, the dns checks out, but, when I try to add a new user account I get the following message...

Windows cannot verify that the user name is unique because the following error occured while contacting the global catalog: The server is not operational.

Windows will create this user account, but the user can log on only after the user name is verified to be unique.  Make sure the global catalog is avalable.


Thanks a ton guys, this sucks.
LVL 2
SlickTechAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Jay_Jay70Commented:
your 2003 machine needs to be a global catalog....you will also need to remove traces of the old DC
http://www.petri.co.il/delete_failed_dcs_from_ad.htm
and make sure the FSMO Roles are intact
http://support.microsoft.com/?id=234790
....a DCDIAG here would be nice (From server 2003 support tools)


0

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
robjeevesCommented:
Hi mate

Sounds like the 2000 was the Domain GC.  Make your 2003 a GC by following the following link.  You might want to check out the FSMO roles also if this wasn't part of your Server install.  You may need to seize some if the 2000 held some and is dead and took some FSMO with it

GC - http://support.microsoft.com/kb/313994

FSMO info
http://www.windowsnetworking.com/articles_tutorials/Managing-Active-Directory-FSMO-Roles.html
And getting the seizing underway, http://support.microsoft.com/kb/324801
0
robjeevesCommented:
Damn you James and your slick keyboard skills :)
0
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.

Jay_Jay70Commented:
lol all good fun mate :)
0
aniesmCommented:
did you remove the old windows 2000 server from the dc list. If no remove the server entry  using the dsutil.  can you please provide the fsmo roles in the forest ? Change the windows 2003 as PDC and also select the gc option in that server.
0
SlickTechAuthor Commented:
Thanks guys, I'll try those in the AM
0
SlickTechAuthor Commented:
Thanks guys, I was scared it wouldnt work because the old catalog server was permenatly offline.  These directions took that into account.  This has been a thorn in my side for quite some time.

Dan
0
robjeevesCommented:
Cool - Glad it worked for you.
0
Jay_Jay70Commented:
sweet as :)
0
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
Microsoft Legacy OS

From novice to tech pro — start learning today.