taking a long time during network connection??

  • Thread starter Thread starter Jim Breon
  • Start date Start date
J

Jim Breon

It is taking 9 to 10 minutes during network connection
which seemed to start several weeks ago and I can't figure
out what is going on.. I think I isolated it to NTDS ISAM
Logging/Recovery event... looking in the Event Viewer I
noticed this in the Directory Service. However, I don't
know how to resolve... Can this event be skipped?? Where
is the log located? It appears to be running 9 minures
from start to end so that could account for a most of the
excess time during the network connection time frame..
total time from start up until the ctrl-alt-del menu is 12
min 12 seconds... so if I can figure out how to handle the
above mentioned NTDS ISAM event maybe it will help cut
back on some Initializaton time... Any one have any ideas
or have run into a simular problem...
Thanks, Jim
PS I have one domain controller and I am running windows
2000 advanced server...
 
Jim,

These delays during start up are many times caused by incorrect DNS
configuration. Make sure the computers having this problem are configured
to use ONLY DNS servers that have a zone for your AD domain (pupulated with
its records which includes 4 sub-folders).

Thanks.

This posting is provided "AS IS" with no warranties, and confers no rights.

Romano Jerez
Microsoft Corporation
 
Jim,

If your server is hanging at preparing network connections at reboot, the
ntds isam errors may be symptomatic and not the root cause of the problem.
Most of time, when computers hang at preparing network connections at
reboot, the problem is caused by a misconfigured DNS. Make sure that your
Windows 2000 domain controller is running DNS and is pointing only to itself
for DNS. Do not have it point out to your ISP directly or to any other DNS
server. This is usually what causes the long delay because the domain
controller tries to register its records in DNS repeatedly before timing
out. Make sure that the clients and servers in your domain also point only
to your domain controller for DNS. You can then configure your domain
controller's DNS server to forward DNS queries that it cannot resolve out to
your ISP. That is the correct way to configure DNS. If yours is not
configured that way, try it and see if that resolves the problem.

Ray Lava
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights
 
Back
Top