Server 2003 FSMO roles reported wrong

We have a statewide network, with each office having a 2003 AD server as a backup.  At our hq, we have  the main 2003 AD server.
Recently, we had problems with the original server.  Rolese were transerverd to our ms-vicksburg server from the original AD ms-dc1.  Now, we have a new 2003 server box ms-dc.  We transfered the roles to this box, and everything seems to be replicating through the districts.
Recently, trying to add a user to a computer, AD said on ms-dc that the user was there.  However, when trying to add him, it would not.  Looking at ms-dc1's AD, the user was not there.
I did a netdom query fsmo roles, and everything is pointing to the ms-vicksburg server.  However, do the same on the ms-dc, and everything is pointing to the ms-dc server.
Is there any way to without removing AD from ms-dc1 to force it to look at ms-dc?  I would like to keep dc1 as a backup for the main server.
Thanks.
Heath CalhounAsked:
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.

RobinHumanCommented:
Use Ntdsutil to sieze the FSMO role
see http://support.microsoft.com/kb/255504
0
Heath CalhounAuthor Commented:
All other servers are showing ms-dc as the 5 FSMO's.  Just ms-dc1 is still showing ms-vicksburg as the holder of the FSMO's.  I used the GUI's to transfer from vicksburg to dc.
0
RobinHumanCommented:
Possiblt because ms-dc1 was the original role holder, it has not registered the change from ms-vicksburg to the new role master; try setting the roles back to dc1 and then transferring them to the new primary
0
Heath CalhounAuthor Commented:
Wound up having to do a forceremoval of dc1 server.  Then did a meta cleanup.  Had one issue moved user shares to new server, gave everyone read of the root shares, but no one could modify their files.  Found I had to give  domain users instead read rights.  That fixed that problem.  I did not have domain users on dc1.  Wonder if it was because it was a dc.
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
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.