I'm actually using Server 2003 but this is still related to Server 2000. As background, I used to have this issue when I worked at a large company with six sites across the country running NT 4.0. Sometime, wokstations would choose a domain controller at a remote site as logon servers and this would casue very very slow logins. It was supposed to mean the local controllers were too busy but that wasn't the case. Anyway, we usedthe setprfdc.exe and lmhost file to solve this.
Question: I work at a small company with two sites connected via a T1. I just setup two controllers at the primary site and a one secondary at the remote location. Anyway, very few people are using these new servers so traffic is low, but when I logged on my login script ran very slowly from the remote site. Can I set the preferred DC's in a policy or what should I do? The local dc were not busy so I'm not sure why it went remotely for logon. I really never want that to happen. if both our DC at the primary site are unavailable we are having major issues that the remote site login would not solve.
I hoped this was solved with AD ?