Newly added Windows Server 2003 Domain Controller won't authenticate anything

I have a Windows Server 2003 network that had only one domain controller.  I have recently promoted another server on the domain to function as a second domain controller and a second DNS server.   When I power down the original domain controller and try to log into the domain on a workstation that is part of the domain, I get the error that no domain controller is available to authenticate and network resources are not available.  Why won't the second domain controller provide the authentication?

The new DC is also a Global Catalog server and I installed DNS on the new DC as well.  I put in the address of the new DC for DNS in my DHCP scope and still it wont authenticate.  I even tried a fixed address and DNS and that does not work either.  I can however pull up Active Directory Users and Computers on both DCs to access AD; the only problem is that the second DC will not authenticate anything when the original is turned off.  I cant think of anything else to try.
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.

Have you confirmed that the SYSVOL folder has replicated successfully to the second DC?

You said you had added the second server as the secondary DNS address in your client's DHCP scope, but have you done a "ipconfig /release && ipconfig /renew" on a client to confirm that it is pulling down the proper data?

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
Darius GhassemCommented:
Try to do an ipconfig /flushdns. Are you getting any errors in the Event Log of the new DC. Do a netdiag /fix then a netdiag then post results.
RecompLLCAuthor Commented:
dfxdeimos,  You are correct, the SYSVOL folder is not being properly replicated that must be the problem.  Any suggestions on how I can get this folder to replicate properly?  What whould happen if I manually copied the data in this folder and subfolders to the new DC?

Regarding the DHCP scope, yes I did make sure the clients were releasing and renewing and getting the proper information.
Darius GhassemCommented:
The burflag method will replicate the SYSVOl.
Dariusq is correct, the method he posted should help you resolve the SYSVOL replication issue, which in turn should solve your root issue.
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.