Server slow to boot up...

Discussion in 'Server Networking' started by Mike, Apr 13, 2006.

  1. Mike

    Mike Guest

    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-
     
    Mike, Apr 13, 2006
    #1
    1. Advertisements

  2. Hi Mike,

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

    Do you have any antivirus software running in this domain controller?
     
    Miha Pihler [MVP], Apr 13, 2006
    #2
    1. Advertisements

  3. 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
     
    Louis Vitiello Jr., Apr 13, 2006
    #3
  4. Mike

    Mike Guest

    Not sure-I'll check tomorrow.
     
    Mike, Apr 14, 2006
    #4
  5. Mike

    Mike Guest

    No, it's just a plain ol' Win2k server, no Exchange, Samll Busines, etc.
     
    Mike, Apr 14, 2006
    #5
  6. Hey Mike,

    Any errors in the Event Viewer?

    Cheers,

    --
    Louis Vitiello Jr.
    ------------------------------
    MCSE, MCSA, MCP, A+/N+
    ERCP XP Pro / Net Concepts
     
    Louis Vitiello Jr., Apr 14, 2006
    #6
  7. 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.aspx?scid=kb;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

     
    Miha Pihler [MVP], Apr 17, 2006
    #7
  8. Mike

    Mark Cuss Guest

    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
     
    Mark Cuss, May 27, 2006
    #8
  9. 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.
     
    Miha Pihler [MVP], May 29, 2006
    #9
  10. Mike

    Mark Cuss Guest

    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
     
    Mark Cuss, May 29, 2006
    #10
  11. Hi,

    to check the DNS settings open DNS MMC. Expand the Forward Lookup Zone and
    right click on the name of your zone. Select the properties for the zone and
    here you should see three buttons. Under Type it should say Active Directory
    Integrated. If it is not -- click on Change button and change the setting.

    Make sure that both servers use AD Integrated zones.
     
    Miha Pihler [MVP], May 30, 2006
    #11
  12. Mike

    Mark Cuss Guest

    Right - both are set for AD Integrated... If they're set for AD, am I
    correct to assume that I don't need to set up the DNS Zone Transfer stuff as
    this is already being handled by AD?

    Mark
     
    Mark Cuss, Jun 1, 2006
    #12
  13. Mike

    Mark Cuss Guest

    Both of my machines are set up as AD Integrated? Am I correct to assume that
    I don't need to set up the Zone Transfers tab on each DNS server as this is
    already handled by AD?

    Thanks
    Mark
     
    Mark Cuss, Jun 1, 2006
    #13
  14. True, in this case you don't have to manually set up Zone Transfer.
     
    Miha Pihler [MVP], Jun 1, 2006
    #14
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.