I concur... do a hunt through all of the subfolders in your AD zone, and delete all references to the old DC's name or IP address. If you gave the address to a new server, remove the entries anyway, and then restart the netlogon service on the new server, and run ipconfig/registerdns on the new server for good measure. Glenn Sullivan, MCSE+I MCDBA David Clark Company Inc. ________________________________ From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Kenzig http://thin.net Posted At: Tuesday, June 22, 2004 9:23 AM Posted To: Windows 2000 Conversation: [windows2000] Re: Excessive logon times?? Subject: [windows2000] Re: Excessive logon times?? Check your DNS -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx]On Behalf Of Jeff Malczewski Sent: Tuesday, June 22, 2004 9:09 AM To: 'windows2000@xxxxxxxxxxxxx' Subject: [windows2000] Excessive logon times?? On Windows 2000 and XP Pro clients, we are seeing times in excess of 15 to 20 minutes before the user reaches their desktop. This is only from standalone PCs, not from Terminal Services sessions. It is not happening to everyone. For instance, I can log in fine from my desk, but my boss, who has the same permissions, same OU, same GPO, same switch card on the backbone, everything, has to wait 15 to 20 minutes to get his desktop... 9x clients get a message stating "Unable to load <DC>\netlogon\config.pol. Please contact your system administrator." Can anyone provide any insight? I removed an AD controller yesterday, but according to ADSIEdit, LDP, and ntdsutil, the removal went just fine, no issues. Help!! Thanks, Jeff This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.