<div>
Questions:<br />
Have you installed the correct drivers for the NIC? &nbsp;<br />
Are you able to ping valid network IP addresses? &nbsp;<br />
Is your IP address a valid network IP address? &nbsp;<br />
What is returned when you nslookup your AD DNS suffix?
</div>


<div>
Yes, sounds like either nic not working right or DNS not pointing to DC.
</div>


<div>
The drivers were installed. &nbsp;I am able to ping addresses. &nbsp;Below is what I get when I ran NSLOOKUP Foughty.local:<br />
C:\Windows\system32&gt;nslook<wbr />up foug<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
Server: &nbsp;UnKnown<br />
Address: &nbsp;10.10.69.152<br />
<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
DNS request timed out.<br />
&nbsp; &nbsp; timeout was 2 seconds.<br />
*** Request to UnKnown timed-out<br />
<br />
The address is wrong. &nbsp;Where would I change that at?
</div>


<div>
I ran nslookup foughty.local from the server and received:<br />
Server: &nbsp;Localhost<br />
Address: &nbsp;127.0.0.1<br />
<br />
Name: &nbsp;Foughty.Local<br />
Address: &nbsp;10.69.69.152<br />
<br />
I cannot access any of the Active Directory sites since the NIC was installed. &nbsp;
</div>


<div>
Start / Control Panel / Network Connections<br />
right click on your NIC / Properties<br />
highlight Internet Protocol (TCP/IP)<br />
click Properties<br />
Enter the proper IP and DNS entry information for your network
</div>


<div>
Also, if this is a lone AD server then you should use its own internal IP as its primary DNS entry.
</div>


<div>
None of the suggestion above are working. &nbsp;Everytime I restart it comes back and says that one service failed at startup and I cannot access AD.
</div>


<div>
Let me give some more information. &nbsp;The NIC that I installed was a second NIC configured for another network address. &nbsp;I have two network segments. &nbsp;10.10.69.x and 10.69.69.x. &nbsp;The Exchange Server is on 10.69.69.x. &nbsp;I was attempting to get the two segments to see each other. &nbsp;I had bridged the two together and that is when the exchange server / domain went down. &nbsp;I have since deleted the bridge, uninstalled the new card and I still cannot access AD or Exchange. &nbsp;<br />
<br />
In DNS the Name Server (NS) entry just has harbor40. instead of harbor40.foughty.local. &nbsp;If enter harbor40.foughty.local it just creates a new entry of harbor40. &nbsp;<br />
<br />
What have I done?
</div>


<div>
I guess you'll only make that mistake once. &nbsp;I finally gave up and rebuilt the server. &nbsp;Thanks to all for your assistance..
</div>


<div>
<div class="content wysiwyg-content">
I started receiving an error message today after installing a new NIC. &nbsp;When I rebooted the server I received a message about a service not starting up. &nbsp;When I try to access AD I get a message of &quot;Naming Information cannot be located because: &nbsp;The logon attempt failed. &nbsp;Contact your system administrator to verify that our domain is properly configured and is currently online.&quot; &nbsp;When I start Exchange 2007 I get the error message of &quot;No Suitable Domain Controller was found in domain Foughty.Local.&quot; &nbsp;I only have one server, which is my DC, Exchange Server and Blackberry Enterprise Server.&quot; &nbsp;Any ideas?
</div>
</div>


I started receiving an error message today after installing a new NIC.  When I rebooted the server I received a message about a service not starting up.  When I try to access AD I get a message of "Naming Information cannot be located because:  The logon attempt failed.  Contact your system administrator to verify that our domain is properly configured and is currently online."  When I start Exchange 2007 I get the error message of "No Suitable Domain Controller was found in domain Foughty.Local."  I only have one server, which is my DC, Exchange Server and Blackberry Enterprise Server."  Any ideas?

No Suitable Domain Controller Error

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.