another Slow Boot question

  • Thread starter Thread starter Jon Simmons
  • Start date Start date
J

Jon Simmons

I have had a win2000 AD domain setup for about a year. I have a single
domain controller which is a Dell PowerEdge 2650 (Dual P4 Xeon, 512Mb, bla
bla), this machine also runs Exchange 2000 as well as AD Integrated DNS.
Since installing AD boot time has been slow, on the order of about 15
minutes. I was told that this long boot time had something to do with
Active Directory and it was normal so I live with it.

Recently I upgraded the RAM in the server to 1.5Gig and Boot time has more
then doubled, it now takes over 30 minutes to boot!

There are no errors logged during boot and DNS seems to be working fine.
What's the deal? Is there something I should be looking for to help fix
this problem, is there anything I can do?


Thanks
Jon
 
Since installing AD boot time has been slow, on the order of about 15

Booting the server or a client?

I was told that this long boot time had something to do with
Active Directory and it was normal so I live with it.


Wrong. This is NOT normal. It is evidence of miscinfigured DNS though.
Listing your ISP's DNS server on the clients would cause this.

Don't think MS would be in business long if their "new" operating system
takes 15 minutes to load everyone would stay with NT 4.0.

Basically point the AD DNS server to itself for DNS in the properties of
TCP/IP, point all AD clients to the AD DNS server ONLY. Set up your AD DNS
server to forward requests and list your ISP's DNS server as the forwarder.
This is the only place your ISP's DNS server should be listed on your
domain.
See:

How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



hth

DDS W 2k MVP MCSE
 
server


Thanks I will check to ensure that these things are all as you describe
below.

Jon
 
Update:

I checked the items you listed below, with the exception of my clients
DNS being pointed at my AD and then my ISP everything you list is set
correctly. (I fixed it in DHCP) I don't imagine that a misconfigured DNS
on a client would cause the server to take 30 minutes to boot, would it?

I read the articles you listed (before I read your post) and my DNSs are
configured as they describe.

Any other suggestions?


Thanks alot for your help
Jon
 
I don't imagine that a misconfigured DNS
on a client would cause the server to take 30 minutes to boot, would it?


No.

Not sure what is causing the slow down

DDS
 
Back
Top