Discussion Locked

Slow logon in W2k AD Domain

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have created a test Windows 2000 AD Domain. The problem I am having is when I change the domain membership of a pc it takes up to 40 minutes for the pc/user to logon to the AD domain. It makes no difference to the logon time if I apply a group policy or not. The only way around it that I have found is to re-install the OS ( W2k Pro ) and join the AD domain as part of the install.
Is there an easier way to get around this problem? I have 150 pc's to move to the new AD domain.

3 replies

by kennethaj

Yes there is a way around the problem, and it is by design. If all of the PC's are Windows 2000, the DNS settings of the workstations must point to the Active Directory server. The server shold also be configured to forward any requests that it can't handle and external DNS. If any DNS requests cannot be handled by the server (such as external/internet requests...eg.-www.yahoo.com), the server would then forward the requests to the internet. To setup forwarding, enable forwarders ate the ADserver and enter the DNS you would like to use.
As for the workstations, they will log on immediately, and AD will work as it was designed to work. Do not put any secondary DNS addresses in the workstation network configuration unless they pointto another AD server on your domain.
This issue is not a fault of win2K but built in by design.

This discussion is closed to new replies.