Active Directory Logins

[bryan]

Can anyone explain why a new Windows 2000 active
directory installation causes Windows XP/2000 machines to
login incredibly slow? It is only a lab test for an
upcoming domain installation, but I would like to have it
go as smoothly as possible. Thank you.

 

[Herb Martin]

Can anyone explain why a new Windows 2000 active
directory installation causes Windows XP/2000 machines to
login incredibly slow? It is only a lab test for an
upcoming domain installation, but I would like to have it
go as smoothly as possible. Thank you.

First place to look is Name Resolution -- especially DNS.

DNS must be dynamic
DNS entry on clients and SERVERS must include ONLY references to this
dynamic DNS (set) -- do NOT include external DNS servers on the clients
and remember that "servers, especially DCs and DNS servers themselves
are
clients TOO."

 

[Jeremy]

Start by running dcdiag and netdiag.
Next run gpresults and as Herb mentioned, make sure that SRV records are
being registered in the DNS. Also, many times in a lab environment you may
not have access to the internet to resolve root level dns records. This to
can cause slow logon response. If this is the case, add a new primary
standara zone called . (as in period). this denotes the desirse for haosting
the root internally.

Jeremy

 

[Herb Martin]

If you are not on the Internet and only have a single domain (no true
hierarchy), it is probably best to forego the "." zone and just check off
the Advanced Properties to DISABLE RECURSION.

 

[Cary Shultz [MVP]]

-----Original Message-----
If you are not on the Internet and only have a single domain (no true
hierarchy), it is probably best to forego the "." zone and just check off
the Advanced Properties to DISABLE RECURSION.

--
Herb Martin


.

Bryan,

I also might throw a couple of MSKB Articles your way
which show you how all important DNS is for WIN2000 /
WINXP Clients.

WIN2000
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

WINXP
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

Additionally, I would take a look at setting up Sites in
your Domain. Granted, with only one Site ( err, there I
go again, assuming.... ) you can technically get away
with out setting up the Site, creating the Subnets and
then associating the Subnet(s) with the appropriate Site
(s) but you might as well do it "correctly".

Here is the MSKB Article on this:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;318480

And just in case you will have multiple Sites:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;316812

http://support.microsoft.com/default.aspx?scid=kb;en-
us;271997&Product=win2000

http://support.microsoft.com/default.aspx?scid=kb;en-
us;224815&Product=win2000

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

There are often a good number of posts concerning clients
from one Site actually authenticating against a DC in
another Site. The last link provided addresses this
issue.

HTH,

Cary