Recently, I have few sites having issue whereby the client machines are going to different domain controller randomly for authentication rather than the local domain controller on-site which is nearly to the clients.
Using domain account A and login to the client machine for 5 times, the logon server randomly hop between 3 different domain controller which include the local domain controller which is the ideal one.
The impact are as follow:
1. Client machine boot up slow. Took about 3mins before the logon screen appears..
2. Slow login.
3. Random Logon server that affect logon script if you are using %logonserver% variable.
Among all the sites I have, there are only a few sites having such issue. Initially, I was thinking if it is a network related issue but after troubleshooting with my network engineer, I am wrong.
I went ahead to search for solution from the Internet and tested out the tools which they suggested like dcdiag.exe and replmon.exe where everything pass and indicates that the local DC is fine.
So.. What can be the issue? 🙂
Oh.. not to mention that I have demo and promo the local DC but the issue still persist!..
I think it will be good for me to blog on this case study as really dive back to the fundamental in order to find out the cause of this issue and resolve it in the end. Haha.
You guys just think what could be the cause. I will disclose the what I did in the next post. 🙂
Time to Sleep…
Note: it is a AD 2003 environment where my DCs are running on Windows Server 2003 and Clients are running on Windows XP SP2\SP3 (Joined to a domain).