Issues on domain when shutting down old DC

We recently added a new domain controler, as well as a new dedicated terminal server, to a network.  After moving over DNS, DHCP, FSMO roles, files and shares, we shut down the old DC before running DC promo on it as a test.  Everything was fine for a couple of hours, but then they started having problems.  Outlook would not connect, instead, it gave users the message "outlook is requesting data from the server".  Users could not log in to the terminal server.  When we turned it back on, everything came back up.  Any ideas on what we should look at?
johnpatbullockAsked:
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.

johnpatbullockAuthor Commented:
Both the Exchange and Terminal servers were configured to look at teh old server for DNS.  I just fixed this.  We will test again shortly to see if that clears this up.
0
Timothy McCartneySYS ADMINISTR I INFRASCommented:
It's very likely that that is the issue. We had a very similar problem with one of our clients. Their primary DC had started having issues with AD, so we moved the role to another server, however the issue wasn't fixed until we realized the DNS settings needed to be adjusted.
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
Suliman Abu KharroubIT Consultant Commented:
As a post DC promotion process, run dcdiag in the new DC to test dc functionality.
0
MAS (MVE)EE Solution GuideCommented:
change the dns address in exchange network card and run the below command
setup.com /prepareAD
0
johnpatbullockAuthor Commented:
Yes, that was the problem.  We've been running smoothly since then.  Thanks for the help.
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
Active Directory

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.