Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 638
  • Last Modified:

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.
0
RecompLLC
Asked:
RecompLLC
  • 2
  • 2
2 Solutions
 
dfxdeimosCommented:
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?
0
 
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.
0
 
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.
Thanks,
0
 
Darius GhassemCommented:
The burflag method will replicate the SYSVOl.

http://support.microsoft.com/kb/315457/
0
 
dfxdeimosCommented:
Dariusq is correct, the method he posted should help you resolve the SYSVOL replication issue, which in turn should solve your root issue.
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now