Windows Forum

Ask something
Discussion Locked

Win2K domain-slow logon

0 helpful
16 replies

by Member 20431980

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am in the process of setting up my first WIN2K Domain. Domain users are taking 11 MINUTES to be logged on and authticated by the server. Can this be normal? Any suggestions on how to speed things up?

16 replies

by cg it

11 minutes? No, that is not normal. Suggestions? Maxwell Edison, Anna or Lordinfidel may have some very useful advise on different actions that you might take to determine just what is the bottleneck.

by xpertdragon

Makre sure that all network settings are correct and effecient, so that your domain users are able to authenticate to the domain controller a little quicker.

Also check into the fact that many of your users maybe using Roaming profiles, whichcan slow down log on authentication.

Paul

by noufal

chack the dns setting at client for profesional computer and wins for others.enable dynamic update for the dns zone .install wins on windows domain controller.

by jamrock

make sure the server and user have the same default protocal. eg if the server is only using TCP/ip then wksta should only loading tcp/ip, remove any other protocal that you are not using. also Make sure they are using the same DNS and DNS is configure properly with forward lookup on the server.

by timwalsh

No, this is not normal at all.

What client OS are you using?

Where is your DNS being hosted, in-house, or by an ISP?

Here is what I suspect:

Your DNS is being hosted by an ISP and NOT in-house.

Active Directory relies heavily on DNS to operate correctly. The DNS server you specify MUST be hosting your DNS domain. The DNS server you specify MUST accept dynamic updates. If you are using your ISP's DNS server, it probably does neither.

Active Directory enters records into DNS that specify where the Domain Controllers (DCs) are located. Your ISP's DNS server either doesn't recognize these entries or will not accept them and thus cannot resolve any queries related to it. Thus your clients are trying to find the DC for your domain and not finding it (at least not easily).

by Member 20431980

Clients are WIN2K Pro. I am not even trying to get internet access yet, just classroom student user authentication. I am running a local DC and I am hosting DNS on my the DC. I have the clients pointing right to the server's IP address for DNS service. I've disabled any group policy from being applied during log on in case that was bogging things down.

This discussion is closed to new replies.