<div>
Thanks for the clarification - I just got the old server online with Mkline71 help and will keep working on it<br />
<br />

</div>


Thanks for the clarification - I just got the old server online with Mkline71 help and will keep working on it



<div>
<div class="content wysiwyg-content">
Hi Yesterday my server crashed and if you look at my history I have had some great help trying to get it restored. <br />
<br />
On my secondary server I though I had AD replicated. When my main AD server crashed nobody can authenticate on the second server and I cannot open AD - it says domain not found.<br />
<br />
I tried to configure DHCP on this machine and got basically the same message - &quot;cannot contact AD&quot;<br />
<br />
My DNS seems okay on my second server and I configured the users to point to it and my gateway.<br />
<br />
I ended up configureing my router to be a DHCP just to get empoyees online again.<br />
<br />
Nobody can access my second server (Dell2) and AD is not showing up.<br />
<br />
I am asuming this is where I have to sieze (or transfer) the rolls over to this server. <br />
<br />
Whts the point of having ad replicated to two servers if one fails and you have to do all this? Or am I missing some basic knowledge or configured it wrong?<br />
<br />
Thanks<br />
<br />

</div>
</div>


Hi Yesterday my server crashed and if you look at my history I have had some great help trying to get it restored. 

On my secondary server I though I had AD replicated. When my main AD server crashed nobody can authenticate on the second server and I cannot open AD - it says domain not found.

I tried to configure DHCP on this machine and got basically the same message - "cannot contact AD"

My DNS seems okay on my second server and I configured the users to point to it and my gateway.

I ended up configureing my router to be a DHCP just to get empoyees online again.

Nobody can access my second server (Dell2) and AD is not showing up.

I am asuming this is where I have to sieze (or transfer) the rolls over to this server. 

Whts the point of having ad replicated to two servers if one fails and you have to do all this? Or am I missing some basic knowledge or configured it wrong?

Thanks



Active Directory Server Failure

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).