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.
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.