Server slow to boot up...

I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
5 client computers connect to it, in a small office LAN.
The problem is that it takes an extremely long time to boot, like several
minutes.
It points to itself for DNS & has forwarding set to the ISP's DNS servers.
How can I speed this up & what could be causing it to be so slow to boot up?
Thanks-

Hi Mike,

Do you have only one domain controller/active directory DNS server?

Do you have any antivirus software running in this domain controller?

--
Mike
Microsoft MVP - Windows Security

"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
> 5 client computers connect to it, in a small office LAN.
> The problem is that it takes an extremely long time to boot, like several
> minutes.
> It points to itself for DNS & has forwarding set to the ISP's DNS servers.
> How can I speed this up & what could be causing it to be so slow to boot
> up?
> Thanks-
>

To add to Mike's questions, does it have Exchange on it?
Small Business Server?

--
Louis Vitiello Jr.
------------------------------
MCSE, MCSA, MCP, A+/N+
ERCP XP Pro / Net Concepts




"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Mike,
>
> Do you have only one domain controller/active directory DNS server?
>
> Do you have any antivirus software running in this domain controller?
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Mike" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
>> 5 client computers connect to it, in a small office LAN.
>> The problem is that it takes an extremely long time to boot, like several
>> minutes.
>> It points to itself for DNS & has forwarding set to the ISP's DNS
>> servers.
>> How can I speed this up & what could be causing it to be so slow to boot
>> up?
>> Thanks-
>>
>
>

"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Mike,
>
> Do you have only one domain controller/active directory DNS server?

Yes

>
> Do you have any antivirus software running in this domain controller?

Not sure-I'll check tomorrow.

>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Mike" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
>> 5 client computers connect to it, in a small office LAN.
>> The problem is that it takes an extremely long time to boot, like several
>> minutes.
>> It points to itself for DNS & has forwarding set to the ISP's DNS
>> servers.
>> How can I speed this up & what could be causing it to be so slow to boot
>> up?
>> Thanks-
>>
>
>

No, it's just a plain ol' Win2k server, no Exchange, Samll Busines, etc.


"Louis Vitiello Jr." <louv-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> To add to Mike's questions, does it have Exchange on it?
> Small Business Server?
>
> --
> Louis Vitiello Jr.
> ------------------------------
> MCSE, MCSA, MCP, A+/N+
> ERCP XP Pro / Net Concepts
>
>
>
>
> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Mike,
>>
>> Do you have only one domain controller/active directory DNS server?
>>
>> Do you have any antivirus software running in this domain controller?
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "Mike" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
>>> 5 client computers connect to it, in a small office LAN.
>>> The problem is that it takes an extremely long time to boot, like
>>> several minutes.
>>> It points to itself for DNS & has forwarding set to the ISP's DNS
>>> servers.
>>> How can I speed this up & what could be causing it to be so slow to boot
>>> up?
>>> Thanks-
>>>
>>
>>
>
>

Hey Mike,

Any errors in the Event Viewer?

Cheers,

--
Louis Vitiello Jr.
------------------------------
MCSE, MCSA, MCP, A+/N+
ERCP XP Pro / Net Concepts



"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> No, it's just a plain ol' Win2k server, no Exchange, Samll Busines, etc.
>
>
> "Louis Vitiello Jr." <louv-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> To add to Mike's questions, does it have Exchange on it?
>> Small Business Server?
>>
>> --
>> Louis Vitiello Jr.
>> ------------------------------
>> MCSE, MCSA, MCP, A+/N+
>> ERCP XP Pro / Net Concepts
>>
>>
>>
>>
>> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hi Mike,
>>>
>>> Do you have only one domain controller/active directory DNS server?
>>>
>>> Do you have any antivirus software running in this domain controller?
>>>
>>> --
>>> Mike
>>> Microsoft MVP - Windows Security
>>>
>>> "Mike" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
>>>> 5 client computers connect to it, in a small office LAN.
>>>> The problem is that it takes an extremely long time to boot, like
>>>> several minutes.
>>>> It points to itself for DNS & has forwarding set to the ISP's DNS
>>>> servers.
>>>> How can I speed this up & what could be causing it to be so slow to
>>>> boot up?
>>>> Thanks-
>>>>
>>>
>>>
>>
>>
>
>

When the server is booting up TCP drivers (services) are loaded quite early.
So now the server will try to talk to DNS server to see if there are any GC
(global catalogs) available. The main problem here is that DNS services are
usually not started yet and since this is your only DNS server it can not
talk to any other DNS server.

Next problem could be if you are using 3rd party NIC drivers -- which
sometimes load late into the boot process which can delay the start of some
TCP related services and DNS server even more...

If you server has antivirus running make sure that it is configured
properly. Here are recommendations for running Antivirus on Domain
Controllers.

Virus scanning recommendations for computers that are running Windows Server
2003, Windows 2000, or Windows XP
http://support.microsoft.com/default...b;en-us;822158

Note: you should have at least two domain controllers for every domain that
is used in production.

I hope this helps,

--
Mike
Microsoft MVP - Windows Security

"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Mike,
>>
>> Do you have only one domain controller/active directory DNS server?
>
> Yes
>
>>
>> Do you have any antivirus software running in this domain controller?
>
> Not sure-I'll check tomorrow.
>
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "Mike" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
>>> 5 client computers connect to it, in a small office LAN.
>>> The problem is that it takes an extremely long time to boot, like
>>> several minutes.
>>> It points to itself for DNS & has forwarding set to the ISP's DNS
>>> servers.
>>> How can I speed this up & what could be causing it to be so slow to boot
>>> up?
>>> Thanks-
>>>
>>
>>
>
>

Miha,

I am having this exact same problem but don't know how to solve it. My
setup is:
- Two Win2k3 SP1 domain controllers for a small domain (~30 clients).
- The first domain controller runs primary DNS and DHCP; the second runs
secondary DNS (ie - via zone transfers from the primary).
- Each domain controller has a fixed IP. The DNS settings in each domain
controller's TCP/IP settings are set to point to the machine itself for the
primary DNS server and to the other domain controller for the secondary DNS
server.

The machines hang for about 10 minutes during the "preparing network
connections" phase. I understand what you're saying about DNS not running
when the other services try to start - I am quite sure that is what is
happening. However, I'm not sure how to make DNS start first! I found a KB
article about making the NetLogon service dependent upon DNS, but that didn't
help...

If you could offer some advice I'd really appreciate it!

Thanks
Mark

"Miha Pihler [MVP]" wrote:

> When the server is booting up TCP drivers (services) are loaded quite early.
> So now the server will try to talk to DNS server to see if there are any GC
> (global catalogs) available. The main problem here is that DNS services are
> usually not started yet and since this is your only DNS server it can not
> talk to any other DNS server.
>
> Next problem could be if you are using 3rd party NIC drivers -- which
> sometimes load late into the boot process which can delay the start of some
> TCP related services and DNS server even more...
>
> If you server has antivirus running make sure that it is configured
> properly. Here are recommendations for running Antivirus on Domain
> Controllers.
>
> Virus scanning recommendations for computers that are running Windows Server
> 2003, Windows 2000, or Windows XP
> http://support.microsoft.com/default...b;en-us;822158
>
> Note: you should have at least two domain controllers for every domain that
> is used in production.
>
> I hope this helps,
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Mike" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >
> > "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Hi Mike,
> >>
> >> Do you have only one domain controller/active directory DNS server?
> >
> > Yes
> >
> >>
> >> Do you have any antivirus software running in this domain controller?
> >
> > Not sure-I'll check tomorrow.
> >
> >>
> >> --
> >> Mike
> >> Microsoft MVP - Windows Security
> >>
> >> "Mike" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
> >>> 5 client computers connect to it, in a small office LAN.
> >>> The problem is that it takes an extremely long time to boot, like
> >>> several minutes.
> >>> It points to itself for DNS & has forwarding set to the ISP's DNS
> >>> servers.
> >>> How can I speed this up & what could be causing it to be so slow to boot
> >>> up?
> >>> Thanks-
> >>>
> >>
> >>
> >
> >
>
>
>

Hi Mark,

If I understand correctly you have problem with slow server boot up.

What you can do for starters is change TCP/IP configuration on your domain
controllers.

On your first domain controller set the preferred DNS server IP address of
the second server instead of pointing it to itself. Do the same on your
second server. Under TCP/IP properties set preferred DNS server IP address
of your primary domain controller.

You will usually not reboot both servers at the same time so once the server
starts to boot it will be able to connect to the DNS service running on the
other server.

My recommendation would also be to use Active Directory Integrated DNS
Zones. This integration will take care of zone replication between both DNS
servers.

I hope this helps you out.

--
Mike
Microsoft MVP - Windows Security

"Mark Cuss" <(E-Mail Removed)> wrote in message
news:7BBD9294-4E0A-4537-AE36-(E-Mail Removed)...
> Miha,
>
> I am having this exact same problem but don't know how to solve it. My
> setup is:
> - Two Win2k3 SP1 domain controllers for a small domain (~30 clients).
> - The first domain controller runs primary DNS and DHCP; the second runs
> secondary DNS (ie - via zone transfers from the primary).
> - Each domain controller has a fixed IP. The DNS settings in each domain
> controller's TCP/IP settings are set to point to the machine itself for
> the
> primary DNS server and to the other domain controller for the secondary
> DNS
> server.
>
> The machines hang for about 10 minutes during the "preparing network
> connections" phase. I understand what you're saying about DNS not running
> when the other services try to start - I am quite sure that is what is
> happening. However, I'm not sure how to make DNS start first! I found a
> KB
> article about making the NetLogon service dependent upon DNS, but that
> didn't
> help...
>
> If you could offer some advice I'd really appreciate it!
>
> Thanks
> Mark
>
> "Miha Pihler [MVP]" wrote:
>
>> When the server is booting up TCP drivers (services) are loaded quite
>> early.
>> So now the server will try to talk to DNS server to see if there are any
>> GC
>> (global catalogs) available. The main problem here is that DNS services
>> are
>> usually not started yet and since this is your only DNS server it can not
>> talk to any other DNS server.
>>
>> Next problem could be if you are using 3rd party NIC drivers -- which
>> sometimes load late into the boot process which can delay the start of
>> some
>> TCP related services and DNS server even more...
>>
>> If you server has antivirus running make sure that it is configured
>> properly. Here are recommendations for running Antivirus on Domain
>> Controllers.
>>
>> Virus scanning recommendations for computers that are running Windows
>> Server
>> 2003, Windows 2000, or Windows XP
>> http://support.microsoft.com/default...b;en-us;822158
>>
>> Note: you should have at least two domain controllers for every domain
>> that
>> is used in production.
>>
>> I hope this helps,
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "Mike" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> >
>> > "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed)...
>> >> Hi Mike,
>> >>
>> >> Do you have only one domain controller/active directory DNS server?
>> >
>> > Yes
>> >
>> >>
>> >> Do you have any antivirus software running in this domain controller?
>> >
>> > Not sure-I'll check tomorrow.
>> >
>> >>
>> >> --
>> >> Mike
>> >> Microsoft MVP - Windows Security
>> >>
>> >> "Mike" <(E-Mail Removed)> wrote in message
>> >> news:(E-Mail Removed)...
>> >>>I have a Win2k server, 2.6GHz P4, 1GB Ram, that is my AD DC.
>> >>> 5 client computers connect to it, in a small office LAN.
>> >>> The problem is that it takes an extremely long time to boot, like
>> >>> several minutes.
>> >>> It points to itself for DNS & has forwarding set to the ISP's DNS
>> >>> servers.
>> >>> How can I speed this up & what could be causing it to be so slow to
>> >>> boot
>> >>> up?
>> >>> Thanks-
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>>

> My recommendation would also be to use Active Directory Integrated DNS
> Zones. This integration will take care of zone replication between both DNS
> servers.

Thanks - this makes sense. However, I'm confused as to how to actually do
this... When I set up the first DC, the wizard automagically installed and
set up DNS and made me an AD integrated zone.

How do I do this on the second DC? I used the Manage Your Server thing to
add the box as a second DC on the domain, but it didn't set up DNS. So I did
it manually - I wasn't sure which options to pick in the wizard though - I
picked the "this domain is managed by another machine" and then manually
configured the zone transfers afterwards, but I don't think this is the
correct way to do it... I'm sure there is something obvious I'm missing
here, but if you could point me in the right direction I'd appreciate it.

Thanks
Mark