<div>
First check that the lan connection shows dns server as itself and secondary as nothing.<br />
If there is second NIC disable it.<br />
What errors show up in the logs?
</div>


<div>
we do have 2 nics<br />
WAN<br />
LAN<br />
Both show the LAN IP as primary DNS. Now the problem with disabling one is when i try it locks up and explore crashes. Causing me to reboot. Starting the process over. Is there away to do it via command line?
</div>


<div>
No way i know of through the command line
</div>


<div>
ok the machine is now back up and functionable. Well sort of. Exchange is still not working and throwing errors out.<br />
<br />
<br />
Event Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Error<br />
Event Source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MSExchangeSA<br />
Event Category: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RFR Interface <br />
Event ID: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9074<br />
Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7/21/2008<br />
Time: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5:21:29 PM<br />
User: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N/A<br />
Computer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PTEXCHANGESVR<br />
Description:<br />
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0]. <br />
<br />
For more information, click <a href="http://www.microsoft.com/contentredirect.asp" rel="ugc">http://www.microsoft.com/contentredirect.asp</a>.<br />
<br />
<br />
<br />
Event Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Error<br />
Event Source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MSExchangeDSAccess<br />
Event Category: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Topology <br />
Event ID: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2114<br />
Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7/21/2008<br />
Time: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5:21:34 PM<br />
User: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N/A<br />
Computer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PTEXCHANGESVR<br />
Description:<br />
Process MAD.EXE (PID=2716). Topology Discovery failed, error 0x8007274c. <br />
<br />
For more information, click <a href="http://www.microsoft.com/contentredirect.asp" rel="ugc">http://www.microsoft.com/contentredirect.asp</a>.<br />
<br />
<br />
Event Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Error<br />
Event Source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MSExchangeMU<br />
Event Category: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;General <br />
Event ID: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1042<br />
Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7/21/2008<br />
Time: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5:21:49 PM<br />
User: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N/A<br />
Computer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PTEXCHANGESVR<br />
Description:<br />
Metabase Update failed to read the Configuration namespace property from the domain controller. Error code is 80040a01. <br />
<br />
For more information, click <a href="http://www.microsoft.com/contentredirect.asp" rel="ugc">http://www.microsoft.com/contentredirect.asp</a>.<br />
<br />
Those are the top 3 that i see in event viewer. Also services MTA stacks, Infomation store and event are not starting. <br />

</div>


<div>
<div class="content wysiwyg-content">
We have had some wierd things come up. Last week our domain controller locked up and needed to be rebooted. It took over 30 minutes to reboot. Once it was back up the only way we could access it was locally. We could ping and surf the internet but no one could see the server locally or via internet. I checked the network connections but it would locked up. So we rebooted again, and again and again. Finally giving up and trying to do some research. Well after about an hour of leaving it alone it finally became accessable remotely. I could ping it via local and internet. BUt then exchange was having nothing but problems (yes i know about exchange on DC but its a small office). Getting errors about namespaces not found and topology errors. I would post some but once again the server is unreachable remotely. Before I put inplace another DC and move exchange over and reformate this machine i wanted to know if there was anyone or anything i could try. I have read numberious microsoft hot fixes but nothing is working. Right now the machine is unreachable and has been for about 45 minutes. PLEASE HELP!!!!!<br />
<br />
<br />

</div>
</div>


We have had some wierd things come up. Last week our domain controller locked up and needed to be rebooted. It took over 30 minutes to reboot. Once it was back up the only way we could access it was locally. We could ping and surf the internet but no one could see the server locally or via internet. I checked the network connections but it would locked up. So we rebooted again, and again and again. Finally giving up and trying to do some research. Well after about an hour of leaving it alone it finally became accessable remotely. I could ping it via local and internet. BUt then exchange was having nothing but problems (yes i know about exchange on DC but its a small office). Getting errors about namespaces not found and topology errors. I would post some but once again the server is unreachable remotely. Before I put inplace another DC and move exchange over and reformate this machine i wanted to know if there was anyone or anything i could try. I have read numberious microsoft hot fixes but nothing is working. Right now the machine is unreachable and has been for about 45 minutes. PLEASE HELP!!!!!




Problems with Domain controller and exchange

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

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

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.