Hello Clayton,
This is normal, it belongs to the problem that during boot the server tries
to reach it's DNS server(own ip address), BUT the DNS server service is not
started at that point. So it goes in a kind of search for DNS servers, after
some time this process stops and it will go on booting. Now the next problem
comes up, AD relies on DNS also but if the DNS server is not fully started,
netlogon etc. can not come up also. If AD is not coming up, Exchange finds
no Global catalog server.
After some time DNS server service is started and the rest will then go on.
AD starts and Exchange will come up also.
Reolution:
In a domain have at least 2 DNS servers to prevent this and configuer them
to use on the NIC the other as primary DNS, you can also set itself primary
and the other secondary, this will slow down the boot process no that much.
In Exchange management console checkalso that all GCs are used from Exchange.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Furthermore I have now added Exchange Server 2007 and it's taking
> longer to startup, 10 minutes later, the system is still loading
>
> "Clayton" <> wrote in message
> news:u6hR$...
>
>> Just installed Windows Server 2008 R2, installed Active Directory
>> services, DNS Server and 1 Domain Controller using DCPromo and after
>> reboot it takes up to 5 minutes to fully load, is this normal?
>>
>> I have put in a static IP and using 127.0.0.1 as a DNS server
>>
>> I have 4GB's of memory a E8400 CPU Dual Core2 3.0GHz and 250GB SATA
>> HDD
>>
>> Thanks
>>