transfer of fsmo roles

i happen to transfer fsmo roles from a windows 2003 32 bit server std to a windows 2008 64 bit
std server.this was successful but some domain controls see the new server with the fsmos roles but some member servers report error under fsmo roles.i have rebooted these servers showing the error but still cant show any changes.can some please help me see what am missing to make the others server point to the new operations mater.

thanks Emma
MRCUGANDAAsked:
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.

Member_6162666Commented:
It sounds like a DNS or replication issue.

Check your DNS settings on the servers that do not see the correct FSMO role holders. Make sure they are pointing to the same DNS servers as the ones that are working properly.

Also, use Active Directory Sites and Services, expand to the replication objects, right-click them, and choose to Replicate Now. Do that for all of them. If you get error messages when yo do that, you have some troubleshooting to do.

Try using repadmin /showreps (you'll need the Windows Server Support Tools package installed) to examine the replication status.
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
SommerblinkCommented:
Agreeded.

Sounds like you had a preexisting AD problem.

I would recommend the above, plus going through event viewer for all your DCs and see if there are errors there that may point towards your problem.
0
Member_6162666Commented:
What astonishes me is that it's even necessary to remind people to do that. But you're right, the event logs might have some good clues.

Also DCDiag and NetDiag in the Windows 2003 Support Tools package are good things to run. You can copy them over to the 2008 server and run them there as well.

Netdiag is deprecated in 2008. Its functions are integrated into the Netlogon service, but you can still copy the .exe from a 2003 server and run it explicitly to look for clues.

0
MRCUGANDAAuthor Commented:
thanks so much for your response.10 mins after i posted i found out it was a dns issue.pointing the other memeber server's dns to the master dns server worked just fine.

thanks again
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
Windows Server 2008

From novice to tech pro — start learning today.